{"id":"CVE-2026-23343","aliases":["AZL-80730","BELL-CVE-2026-23343","CLSA-2026-1786350974","CLSA-2026-1789986443","DEBIAN-CVE-2026-23343","EUVD-2026-15310","GHSA-rqf2-6q66-wgpp","MGASA-2026-0097","MGASA-2026-0098","OESA-2026-1862","OESA-2026-1863","OESA-2026-1864","ROOT-OS-DEBIAN-12-CVE-2026-23343","ROOT-OS-UBUNTU-2404-CVE-2026-23343","SUSE-SU-2026:21114-1","SUSE-SU-2026:21123-1","SUSE-SU-2026:21230-1","SUSE-SU-2026:21237-1","SUSE-SU-2026:21255-1","SUSE-SU-2026:21352-1","SUSE-SU-2026:21361-1","SUSE-SU-2026:2217-1","SUSE-SU-2026:2238-1","UBUNTU-CVE-2026-23343","USN-8567-1","USN-8574-1","USN-8574-2","USN-8574-3","USN-8595-1","USN-8595-2","USN-8595-3","USN-8596-1","USN-8606-1","USN-8607-1","USN-8608-1","USN-8609-1","USN-8619-1","USN-8665-1","openSUSE-SU-2026:20572-1"],"status":"published","title":"xdp: produce a warning when calculated tailroom is negative","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.0014,"percentile":0.03427,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-787"],"published":"2026-03-25T10:27:31Z","modified":"2026-11-10T12:42:38Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.130.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.167-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.80-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.167","6.6.130","6.12.77","6.18.17","6.19.7"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.170-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.85-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.19.8-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1061.64~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1063.71~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1062.69~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1064.72~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-136.136~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1061.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-136.136.2~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1059.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1058.61~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-136.136~22.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1056.57~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-136.136"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1061.64"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1063.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1062.69"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1064.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1059.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1046.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1061.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-136.136.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1059.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1059.62.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1030.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1061.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","fixed_in":["6.8.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1033.34"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1028.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2050.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1056.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1061.64+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1063.71+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-136.136+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1064.72+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.164-r0"},{"fixed":"6.1.167-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.74-r0"},{"fixed":"6.12.80-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els10"}]}],"bundled":119},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els14"}]}],"bundled":121},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.18.0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.7"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.170-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.85-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.19.8-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.115-1","6.12.115-2","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.10-1","6.18.12-1","6.18.12-1~bpo13+1","6.18.13-1","6.18.14-1","6.18.15-1","6.18.15-1~bpo13+1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18.8-1","6.18.9-1","6.18.9-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1","6.19-1~exp1","6.19.2-1~exp1","6.19.3-1~exp1","6.19.4-1~exp1","6.19.5-1~exp1","6.19.6-1","6.19.6-2","6.19.6-2~bpo13+1","6.19.8-1~bpo13+1","6.19~rc4-1~exp1","6.19~rc5-1~exp1","6.19~rc6-1~exp1","6.19~rc7-1~exp1","6.19~rc8-1~exp1"]},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-15.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-89.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.130.oe2403"}]}],"bundled":45},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.142.oe2403sp1"}]}],"bundled":48},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.0.2.143.oe2403sp2"}]}],"bundled":45},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"gdk-pixbuf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.42.12-160000.4.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1.150700.17.33.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":204},{"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.53.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"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.55.1"}]}],"bundled":204},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1057.60~22.04.1","6.8.0-1060.63~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1","6.8.0-1059.65~22.04.1","6.8.0-1062.69~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1","6.8.0-1058.65~22.04.1","6.8.0-1061.68~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1063.69~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1","6.8.0-117.117.1~22.04.1","6.8.0-134.134.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1","6.8.0-1054.55~22.04.1","6.8.0-1057.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.3"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57~22.04.2"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1019.19~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1008.8~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.2","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1020.20~24.04.1","6.17.0-1021.21~24.04.1","6.17.0-1022.22"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32","6.8.0-1039.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1004.4~24.04.3","6.17.0-1008.8~24.04.1","6.17.0-1009.9~24.04.3","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1016.17~24.04.1","6.17.0-1018.19~24.04.1","6.17.0-1020.22~24.04.1","6.17.0-1021.24~24.04.1","6.17.0-1022.25"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.67"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-14.14~24.04.1","6.17.0-19.19~24.04.2","6.17.0-20.20~24.04.1","6.17.0-22.22~24.04.1","6.17.0-23.23~24.04.1","6.17.0-29.29~24.04.1","6.17.0-35.35~24.04.1","6.17.0-40.40~24.04.1","6.17.0-41.41~24.04.1","6.17.0-42.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1","6.8.0-117.117.1","6.8.0-134.134.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14","6.17.0-1018.18","6.17.0-1021.21","6.17.0-1026.26","6.17.0-1029.29","6.17.0-1031.31","6.17.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1017.17","6.17.0-1020.20","6.17.0-1023.23","6.17.0-1024.24","6.17.0-1025.25","6.17.0-1028.28","6.17.0-1030.30","6.17.0-1032.32","6.17.0-1033.33"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53","6.8.0-1054.55","6.8.0-1057.58"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1004.4~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.1","6.17.0-1014.14~24.04.1","6.17.0-1016.16~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1019.19~24.04.3","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.65"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-14.14.1~24.04.1","6.17.0-19.19.1~24.04.1","6.17.0-20.20.1~24.04.1","6.17.0-22.22.1~24.04.1","6.17.0-23.23.1~24.04.1","6.17.0-29.29.1~24.04.1","6.17.0-35.35.1~24.04.1","6.17.0-38.38.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.8"}]}],"versions":["6.8.0-1005.5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1032.33"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.33"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1026.30"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1004.5~24.04.2","6.17.0-1006.7~24.04.1","6.17.0-1008.9~24.04.1","6.17.0-1009.10~24.04.1","6.17.0-1010.11~24.04.1","6.17.0-1011.12~24.04.1","6.17.0-1013.15~24.04.1","6.17.0-1014.16~24.04.1","6.17.0-1017.19~24.04.1","6.17.0-1018.20~24.04.1","6.17.0-1019.22"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71+fips2"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20","6.17.0-22.22","6.17.0-23.23","6.17.0-29.29","6.17.0-35.35","6.17.0-40.40"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1016.17","6.17.0-1018.19","6.17.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1016.16","6.17.0-1018.18"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1014.14","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10","6.17.0-1010.11","6.17.0-1011.12","6.17.0-1013.15","6.17.0-1014.16","6.17.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1","6.17.0-14.14.1","6.17.0-19.19.1","6.17.0-20.20.1","6.17.0-22.22.1","6.17.0-23.23.1","6.17.0-29.29.1","6.17.0-35.35.1","6.17.0-40.40.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1063.69~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57~22.04.2"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.67"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1","6.8.0-117.117.1~22.04.1","6.8.0-134.134.1~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1","6.8.0-117.117.1","6.8.0-134.134.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53","6.8.0-1054.55","6.8.0-1057.58"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1032.33"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1","6.8.0-1054.55~22.04.1","6.8.0-1057.58~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1057.60~22.04.1","6.8.0-1060.63~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+fips1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1","6.8.0-1059.65~22.04.1","6.8.0-1062.69~22.04.1"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"],"bundled":1205},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71+fips2"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"],"bundled":914},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1","6.8.0-1058.65~22.04.1","6.8.0-1061.68~22.04.1"],"bundled":1206},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"],"bundled":1209},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.65"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"],"bundled":912},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 tm mfp - gnu/linux subsystem"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp (6ag1518-4ax00-4ac0)"}],"references":[{"url":"https://git.kernel.org/stable/c/01379540452a02bbc52f639d45dd365cd3624efb","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/a0fb59f527d03c60b2cd547cfae4a842ad84670f","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/c7c790a07697148c41e2d03eb28efe132adda749","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/98cd8b4d0b836d3edf70161f40efd9cbb8c8f252","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/94b9da7e9f958cb3d115b21eff824ecd8c3217aa","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/8821e857759be9db3cde337ad328b71fe5c8a55f","tags":["Patch","web","report"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-082556.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-019113.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-457936.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-784472.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23343","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-rqf2-6q66-wgpp"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23343","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1786350974.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48650","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49388","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49716","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52456","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52849","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53603","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57917","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38593","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39701","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39776","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39860","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23262","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23456","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31639","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31758","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43233","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43339","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53252","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64561","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80676","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1789986443.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53175","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21751","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37743","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23327","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31458","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43092","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43437","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52910","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53250","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53281","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53324","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64210","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64275","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68123","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68253","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68257","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68258","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68296","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68348","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68432","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72472","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74565","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23343.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-23343","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0097.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35281","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.121","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.122","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.123","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.124","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.125","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.126","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.127","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.128","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.129","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.130","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0098.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35282","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68727","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23274","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23278","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23304","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23310","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23368","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23371","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23394","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23397","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31788","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23171","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1864","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621114-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1226591","tags":["report"]},{"url":"https://bugzilla.suse.com/1245728","tags":["report"]},{"url":"https://bugzilla.suse.com/1249998","tags":["report"]},{"url":"https://bugzilla.suse.com/1251135","tags":["report"]},{"url":"https://bugzilla.suse.com/1251186","tags":["report"]},{"url":"https://bugzilla.suse.com/1251971","tags":["report"]},{"url":"https://bugzilla.suse.com/1252073","tags":["report"]},{"url":"https://bugzilla.suse.com/1252266","tags":["report"]},{"url":"https://bugzilla.suse.com/1253049","tags":["report"]},{"url":"https://bugzilla.suse.com/1253455","tags":["report"]},{"url":"https://bugzilla.suse.com/1254306","tags":["report"]},{"url":"https://bugzilla.suse.com/1255084","tags":["report"]},{"url":"https://bugzilla.suse.com/1256645","tags":["report"]},{"url":"https://bugzilla.suse.com/1256647","tags":["report"]},{"url":"https://bugzilla.suse.com/1256690","tags":["report"]},{"url":"https://bugzilla.suse.com/1256784","tags":["report"]},{"url":"https://bugzilla.suse.com/1257183","tags":["report"]},{"url":"https://bugzilla.suse.com/1257466","tags":["report"]},{"url":"https://bugzilla.suse.com/1257472","tags":["report"]},{"url":"https://bugzilla.suse.com/1257473","tags":["report"]},{"url":"https://bugzilla.suse.com/1257506","tags":["report"]},{"url":"https://bugzilla.suse.com/1257561","tags":["report"]},{"url":"https://bugzilla.suse.com/1257682","tags":["report"]},{"url":"https://bugzilla.suse.com/1257732","tags":["report"]},{"url":"https://bugzilla.suse.com/1257755","tags":["report"]},{"url":"https://bugzilla.suse.com/1257773","tags":["report"]},{"url":"https://bugzilla.suse.com/1257777","tags":["report"]},{"url":"https://bugzilla.suse.com/1257814","tags":["report"]},{"url":"https://bugzilla.suse.com/1257952","tags":["report"]},{"url":"https://bugzilla.suse.com/1258280","tags":["report"]},{"url":"https://bugzilla.suse.com/1258286","tags":["report"]},{"url":"https://bugzilla.suse.com/1258293","tags":["report"]},{"url":"https://bugzilla.suse.com/1258303","tags":["report"]},{"url":"https://bugzilla.suse.com/1258305","tags":["report"]},{"url":"https://bugzilla.suse.com/1258330","tags":["report"]},{"url":"https://bugzilla.suse.com/1258337","tags":["report"]},{"url":"https://bugzilla.suse.com/1258338","tags":["report"]},{"url":"https://bugzilla.suse.com/1258340","tags":["report"]},{"url":"https://bugzilla.suse.com/1258376","tags":["report"]},{"url":"https://bugzilla.suse.com/1258389","tags":["report"]},{"url":"https://bugzilla.suse.com/1258414","tags":["report"]},{"url":"https://bugzilla.suse.com/1258424","tags":["report"]},{"url":"https://bugzilla.suse.com/1258447","tags":["report"]},{"url":"https://bugzilla.suse.com/1258524","tags":["report"]},{"url":"https://bugzilla.suse.com/1258832","tags":["report"]},{"url":"https://bugzilla.suse.com/1258849","tags":["report"]},{"url":"https://bugzilla.suse.com/1259188","tags":["report"]},{"url":"https://bugzilla.suse.com/1259461","tags":["report"]},{"url":"https://bugzilla.suse.com/1259580","tags":["report"]},{"url":"https://bugzilla.suse.com/1259707","tags":["report"]},{"url":"https://bugzilla.suse.com/1259795","tags":["report"]},{"url":"https://bugzilla.suse.com/1259797","tags":["report"]},{"url":"https://bugzilla.suse.com/1259865","tags":["report"]},{"url":"https://bugzilla.suse.com/1259870","tags":["report"]},{"url":"https://bugzilla.suse.com/1259886","tags":["report"]},{"url":"https://bugzilla.suse.com/1259889","tags":["report"]},{"url":"https://bugzilla.suse.com/1259891","tags":["report"]},{"url":"https://bugzilla.suse.com/1259997","tags":["report"]},{"url":"https://bugzilla.suse.com/1259998","tags":["report"]},{"url":"https://bugzilla.suse.com/1260005","tags":["report"]},{"url":"https://bugzilla.suse.com/1260009","tags":["report"]},{"url":"https://bugzilla.suse.com/1260347","tags":["report"]},{"url":"https://bugzilla.suse.com/1260464","tags":["report"]},{"url":"https://bugzilla.suse.com/1260471","tags":["report"]},{"url":"https://bugzilla.suse.com/1260481","tags":["report"]},{"url":"https://bugzilla.suse.com/1260486","tags":["report"]},{"url":"https://bugzilla.suse.com/1260497","tags":["report"]},{"url":"https://bugzilla.suse.com/1260500","tags":["report"]},{"url":"https://bugzilla.suse.com/1260527","tags":["report"]},{"url":"https://bugzilla.suse.com/1260544","tags":["report"]},{"url":"https://bugzilla.suse.com/1260550","tags":["report"]},{"url":"https://bugzilla.suse.com/1260562","tags":["report"]},{"url":"https://bugzilla.suse.com/1260580","tags":["report"]},{"url":"https://bugzilla.suse.com/1260730","tags":["report"]},{"url":"https://bugzilla.suse.com/1260732","tags":["report"]},{"url":"https://bugzilla.suse.com/1260735","tags":["report"]},{"url":"https://bugzilla.suse.com/1260799","tags":["report"]},{"url":"https://bugzilla.suse.com/1261412","tags":["report"]},{"url":"https://bugzilla.suse.com/1261496","tags":["report"]},{"url":"https://bugzilla.suse.com/1261498","tags":["report"]},{"url":"https://bugzilla.suse.com/1261507","tags":["report"]},{"url":"https://bugzilla.suse.com/1261669","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31788","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621123-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621230-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1191256","tags":["report"]},{"url":"https://bugzilla.suse.com/1191270","tags":["report"]},{"url":"https://bugzilla.suse.com/1194778","tags":["report"]},{"url":"https://bugzilla.suse.com/1207184","tags":["report"]},{"url":"https://bugzilla.suse.com/1217845","tags":["report"]},{"url":"https://bugzilla.suse.com/1222768","tags":["report"]},{"url":"https://bugzilla.suse.com/1243208","tags":["report"]},{"url":"https://bugzilla.suse.com/1253129","tags":["report"]},{"url":"https://bugzilla.suse.com/1254214","tags":["report"]},{"url":"https://bugzilla.suse.com/1254307","tags":["report"]},{"url":"https://bugzilla.suse.com/1255687","tags":["report"]},{"url":"https://bugzilla.suse.com/1257511","tags":["report"]},{"url":"https://bugzilla.suse.com/1257708","tags":["report"]},{"url":"https://bugzilla.suse.com/1258175","tags":["report"]},{"url":"https://bugzilla.suse.com/1258301","tags":["report"]},{"url":"https://bugzilla.suse.com/1258476","tags":["report"]},{"url":"https://bugzilla.suse.com/1259484","tags":["report"]},{"url":"https://bugzilla.suse.com/1259485","tags":["report"]},{"url":"https://bugzilla.suse.com/1259759","tags":["report"]},{"url":"https://bugzilla.suse.com/1259955","tags":["report"]},{"url":"https://bugzilla.suse.com/1260459","tags":["report"]},{"url":"https://bugzilla.suse.com/1260490","tags":["report"]},{"url":"https://bugzilla.suse.com/1260522","tags":["report"]},{"url":"https://bugzilla.suse.com/1260606","tags":["report"]},{"url":"https://bugzilla.suse.com/1261506","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23425","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621237-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621255-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621352-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621361-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262217-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1225897","tags":["report"]},{"url":"https://bugzilla.suse.com/1234634","tags":["report"]},{"url":"https://bugzilla.suse.com/1237452","tags":["report"]},{"url":"https://bugzilla.suse.com/1241166","tags":["report"]},{"url":"https://bugzilla.suse.com/1243603","tags":["report"]},{"url":"https://bugzilla.suse.com/1248754","tags":["report"]},{"url":"https://bugzilla.suse.com/1249104","tags":["report"]},{"url":"https://bugzilla.suse.com/1253122","tags":["report"]},{"url":"https://bugzilla.suse.com/1253754","tags":["report"]},{"url":"https://bugzilla.suse.com/1254518","tags":["report"]},{"url":"https://bugzilla.suse.com/1255160","tags":["report"]},{"url":"https://bugzilla.suse.com/1255752","tags":["report"]},{"url":"https://bugzilla.suse.com/1256863","tags":["report"]},{"url":"https://bugzilla.suse.com/1257631","tags":["report"]},{"url":"https://bugzilla.suse.com/1258518","tags":["report"]},{"url":"https://bugzilla.suse.com/1258718","tags":["report"]},{"url":"https://bugzilla.suse.com/1258826","tags":["report"]},{"url":"https://bugzilla.suse.com/1258850","tags":["report"]},{"url":"https://bugzilla.suse.com/1258854","tags":["report"]},{"url":"https://bugzilla.suse.com/1258855","tags":["report"]},{"url":"https://bugzilla.suse.com/1258856","tags":["report"]},{"url":"https://bugzilla.suse.com/1258857","tags":["report"]},{"url":"https://bugzilla.suse.com/1258961","tags":["report"]},{"url":"https://bugzilla.suse.com/1259186","tags":["report"]},{"url":"https://bugzilla.suse.com/1259199","tags":["report"]},{"url":"https://bugzilla.suse.com/1259222","tags":["report"]},{"url":"https://bugzilla.suse.com/1259535","tags":["report"]},{"url":"https://bugzilla.suse.com/1259672","tags":["report"]},{"url":"https://bugzilla.suse.com/1259799","tags":["report"]},{"url":"https://bugzilla.suse.com/1259806","tags":["report"]},{"url":"https://bugzilla.suse.com/1259857","tags":["report"]},{"url":"https://bugzilla.suse.com/1259868","tags":["report"]},{"url":"https://bugzilla.suse.com/1259869","tags":["report"]},{"url":"https://bugzilla.suse.com/1259871","tags":["report"]},{"url":"https://bugzilla.suse.com/1259873","tags":["report"]},{"url":"https://bugzilla.suse.com/1259878","tags":["report"]},{"url":"https://bugzilla.suse.com/1259995","tags":["report"]},{"url":"https://bugzilla.suse.com/1260010","tags":["report"]},{"url":"https://bugzilla.suse.com/1260012","tags":["report"]},{"url":"https://bugzilla.suse.com/1260018","tags":["report"]},{"url":"https://bugzilla.suse.com/1260428","tags":["report"]},{"url":"https://bugzilla.suse.com/1260468","tags":["report"]},{"url":"https://bugzilla.suse.com/1260483","tags":["report"]},{"url":"https://bugzilla.suse.com/1260484","tags":["report"]},{"url":"https://bugzilla.suse.com/1260485","tags":["report"]},{"url":"https://bugzilla.suse.com/1260489","tags":["report"]},{"url":"https://bugzilla.suse.com/1260501","tags":["report"]},{"url":"https://bugzilla.suse.com/1260504","tags":["report"]},{"url":"https://bugzilla.suse.com/1260505","tags":["report"]},{"url":"https://bugzilla.suse.com/1260507","tags":["report"]},{"url":"https://bugzilla.suse.com/1260523","tags":["report"]},{"url":"https://bugzilla.suse.com/1260526","tags":["report"]},{"url":"https://bugzilla.suse.com/1260528","tags":["report"]},{"url":"https://bugzilla.suse.com/1260529","tags":["report"]},{"url":"https://bugzilla.suse.com/1260530","tags":["report"]},{"url":"https://bugzilla.suse.com/1260531","tags":["report"]},{"url":"https://bugzilla.suse.com/1260532","tags":["report"]},{"url":"https://bugzilla.suse.com/1260533","tags":["report"]},{"url":"https://bugzilla.suse.com/1260536","tags":["report"]},{"url":"https://bugzilla.suse.com/1260537","tags":["report"]},{"url":"https://bugzilla.suse.com/1260538","tags":["report"]},{"url":"https://bugzilla.suse.com/1260541","tags":["report"]},{"url":"https://bugzilla.suse.com/1260546","tags":["report"]},{"url":"https://bugzilla.suse.com/1260549","tags":["report"]},{"url":"https://bugzilla.suse.com/1260551","tags":["report"]},{"url":"https://bugzilla.suse.com/1260552","tags":["report"]},{"url":"https://bugzilla.suse.com/1260553","tags":["report"]},{"url":"https://bugzilla.suse.com/1260555","tags":["report"]},{"url":"https://bugzilla.suse.com/1260561","tags":["report"]},{"url":"https://bugzilla.suse.com/1260566","tags":["report"]},{"url":"https://bugzilla.suse.com/1260572","tags":["report"]},{"url":"https://bugzilla.suse.com/1260581","tags":["report"]},{"url":"https://bugzilla.suse.com/1260728","tags":["report"]},{"url":"https://bugzilla.suse.com/1260729","tags":["report"]},{"url":"https://bugzilla.suse.com/1260731","tags":["report"]},{"url":"https://bugzilla.suse.com/1260800","tags":["report"]},{"url":"https://bugzilla.suse.com/1260801","tags":["report"]},{"url":"https://bugzilla.suse.com/1260811","tags":["report"]},{"url":"https://bugzilla.suse.com/1260989","tags":["report"]},{"url":"https://bugzilla.suse.com/1261020","tags":["report"]},{"url":"https://bugzilla.suse.com/1261287","tags":["report"]},{"url":"https://bugzilla.suse.com/1261295","tags":["report"]},{"url":"https://bugzilla.suse.com/1261348","tags":["report"]},{"url":"https://bugzilla.suse.com/1261503","tags":["report"]},{"url":"https://bugzilla.suse.com/1261504","tags":["report"]},{"url":"https://bugzilla.suse.com/1261505","tags":["report"]},{"url":"https://bugzilla.suse.com/1261555","tags":["report"]},{"url":"https://bugzilla.suse.com/1261581","tags":["report"]},{"url":"https://bugzilla.suse.com/1261582","tags":["report"]},{"url":"https://bugzilla.suse.com/1261584","tags":["report"]},{"url":"https://bugzilla.suse.com/1261585","tags":["report"]},{"url":"https://bugzilla.suse.com/1261601","tags":["report"]},{"url":"https://bugzilla.suse.com/1261602","tags":["report"]},{"url":"https://bugzilla.suse.com/1261618","tags":["report"]},{"url":"https://bugzilla.suse.com/1261628","tags":["report"]},{"url":"https://bugzilla.suse.com/1261632","tags":["report"]},{"url":"https://bugzilla.suse.com/1261636","tags":["report"]},{"url":"https://bugzilla.suse.com/1261637","tags":["report"]},{"url":"https://bugzilla.suse.com/1261638","tags":["report"]},{"url":"https://bugzilla.suse.com/1261641","tags":["report"]},{"url":"https://bugzilla.suse.com/1261644","tags":["report"]},{"url":"https://bugzilla.suse.com/1261645","tags":["report"]},{"url":"https://bugzilla.suse.com/1261648","tags":["report"]},{"url":"https://bugzilla.suse.com/1261679","tags":["report"]},{"url":"https://bugzilla.suse.com/1261685","tags":["report"]},{"url":"https://bugzilla.suse.com/1261686","tags":["report"]},{"url":"https://bugzilla.suse.com/1261687","tags":["report"]},{"url":"https://bugzilla.suse.com/1261692","tags":["report"]},{"url":"https://bugzilla.suse.com/1261694","tags":["report"]},{"url":"https://bugzilla.suse.com/1261700","tags":["report"]},{"url":"https://bugzilla.suse.com/1261702","tags":["report"]},{"url":"https://bugzilla.suse.com/1261703","tags":["report"]},{"url":"https://bugzilla.suse.com/1261707","tags":["report"]},{"url":"https://bugzilla.suse.com/1261710","tags":["report"]},{"url":"https://bugzilla.suse.com/1261713","tags":["report"]},{"url":"https://bugzilla.suse.com/1261714","tags":["report"]},{"url":"https://bugzilla.suse.com/1261719","tags":["report"]},{"url":"https://bugzilla.suse.com/1261738","tags":["report"]},{"url":"https://bugzilla.suse.com/1261750","tags":["report"]},{"url":"https://bugzilla.suse.com/1261751","tags":["report"]},{"url":"https://bugzilla.suse.com/1261752","tags":["report"]},{"url":"https://bugzilla.suse.com/1261768","tags":["report"]},{"url":"https://bugzilla.suse.com/1261778","tags":["report"]},{"url":"https://bugzilla.suse.com/1261779","tags":["report"]},{"url":"https://bugzilla.suse.com/1261780","tags":["report"]},{"url":"https://bugzilla.suse.com/1261781","tags":["report"]},{"url":"https://bugzilla.suse.com/1261786","tags":["report"]},{"url":"https://bugzilla.suse.com/1261788","tags":["report"]},{"url":"https://bugzilla.suse.com/1261789","tags":["report"]},{"url":"https://bugzilla.suse.com/1261796","tags":["report"]},{"url":"https://bugzilla.suse.com/1261797","tags":["report"]},{"url":"https://bugzilla.suse.com/1261896","tags":["report"]},{"url":"https://bugzilla.suse.com/1262019","tags":["report"]},{"url":"https://bugzilla.suse.com/1262020","tags":["report"]},{"url":"https://bugzilla.suse.com/1262053","tags":["report"]},{"url":"https://bugzilla.suse.com/1262054","tags":["report"]},{"url":"https://bugzilla.suse.com/1262055","tags":["report"]},{"url":"https://bugzilla.suse.com/1262061","tags":["report"]},{"url":"https://bugzilla.suse.com/1262063","tags":["report"]},{"url":"https://bugzilla.suse.com/1262074","tags":["report"]},{"url":"https://bugzilla.suse.com/1262078","tags":["report"]},{"url":"https://bugzilla.suse.com/1262086","tags":["report"]},{"url":"https://bugzilla.suse.com/1262087","tags":["report"]},{"url":"https://bugzilla.suse.com/1262099","tags":["report"]},{"url":"https://bugzilla.suse.com/1262100","tags":["report"]},{"url":"https://bugzilla.suse.com/1262101","tags":["report"]},{"url":"https://bugzilla.suse.com/1262179","tags":["report"]},{"url":"https://bugzilla.suse.com/1262181","tags":["report"]},{"url":"https://bugzilla.suse.com/1262250","tags":["report"]},{"url":"https://bugzilla.suse.com/1262480","tags":["report"]},{"url":"https://bugzilla.suse.com/1262526","tags":["report"]},{"url":"https://bugzilla.suse.com/1262599","tags":["report"]},{"url":"https://bugzilla.suse.com/1262602","tags":["report"]},{"url":"https://bugzilla.suse.com/1262616","tags":["report"]},{"url":"https://bugzilla.suse.com/1262665","tags":["report"]},{"url":"https://bugzilla.suse.com/1262671","tags":["report"]},{"url":"https://bugzilla.suse.com/1262673","tags":["report"]},{"url":"https://bugzilla.suse.com/1262709","tags":["report"]},{"url":"https://bugzilla.suse.com/1262725","tags":["report"]},{"url":"https://bugzilla.suse.com/1262731","tags":["report"]},{"url":"https://bugzilla.suse.com/1262734","tags":["report"]},{"url":"https://bugzilla.suse.com/1262746","tags":["report"]},{"url":"https://bugzilla.suse.com/1262752","tags":["report"]},{"url":"https://bugzilla.suse.com/1262758","tags":["report"]},{"url":"https://bugzilla.suse.com/1263001","tags":["report"]},{"url":"https://bugzilla.suse.com/1263012","tags":["report"]},{"url":"https://bugzilla.suse.com/1263018","tags":["report"]},{"url":"https://bugzilla.suse.com/1263064","tags":["report"]},{"url":"https://bugzilla.suse.com/1263065","tags":["report"]},{"url":"https://bugzilla.suse.com/1263085","tags":["report"]},{"url":"https://bugzilla.suse.com/1263093","tags":["report"]},{"url":"https://bugzilla.suse.com/1263095","tags":["report"]},{"url":"https://bugzilla.suse.com/1263104","tags":["report"]},{"url":"https://bugzilla.suse.com/1263131","tags":["report"]},{"url":"https://bugzilla.suse.com/1263140","tags":["report"]},{"url":"https://bugzilla.suse.com/1263141","tags":["report"]},{"url":"https://bugzilla.suse.com/1263149","tags":["report"]},{"url":"https://bugzilla.suse.com/1263165","tags":["report"]},{"url":"https://bugzilla.suse.com/1263170","tags":["report"]},{"url":"https://bugzilla.suse.com/1263176","tags":["report"]},{"url":"https://bugzilla.suse.com/1263255","tags":["report"]},{"url":"https://bugzilla.suse.com/1263556","tags":["report"]},{"url":"https://bugzilla.suse.com/1263582","tags":["report"]},{"url":"https://bugzilla.suse.com/1263592","tags":["report"]},{"url":"https://bugzilla.suse.com/1263593","tags":["report"]},{"url":"https://bugzilla.suse.com/1263595","tags":["report"]},{"url":"https://bugzilla.suse.com/1263596","tags":["report"]},{"url":"https://bugzilla.suse.com/1263600","tags":["report"]},{"url":"https://bugzilla.suse.com/1263668","tags":["report"]},{"url":"https://bugzilla.suse.com/1263723","tags":["report"]},{"url":"https://bugzilla.suse.com/1263797","tags":["report"]},{"url":"https://bugzilla.suse.com/1263815","tags":["report"]},{"url":"https://bugzilla.suse.com/1263877","tags":["report"]},{"url":"https://bugzilla.suse.com/1263882","tags":["report"]},{"url":"https://bugzilla.suse.com/1263901","tags":["report"]},{"url":"https://bugzilla.suse.com/1263931","tags":["report"]},{"url":"https://bugzilla.suse.com/1263933","tags":["report"]},{"url":"https://bugzilla.suse.com/1263995","tags":["report"]},{"url":"https://bugzilla.suse.com/1264014","tags":["report"]},{"url":"https://bugzilla.suse.com/1264059","tags":["report"]},{"url":"https://bugzilla.suse.com/1264082","tags":["report"]},{"url":"https://bugzilla.suse.com/1264087","tags":["report"]},{"url":"https://bugzilla.suse.com/1264097","tags":["report"]},{"url":"https://bugzilla.suse.com/1264183","tags":["report"]},{"url":"https://bugzilla.suse.com/1264427","tags":["report"]},{"url":"https://bugzilla.suse.com/1264449","tags":["report"]},{"url":"https://bugzilla.suse.com/1264469","tags":["report"]},{"url":"https://bugzilla.suse.com/1264482","tags":["report"]},{"url":"https://bugzilla.suse.com/1264634","tags":["report"]},{"url":"https://bugzilla.suse.com/1264651","tags":["report"]},{"url":"https://bugzilla.suse.com/1264661","tags":["report"]},{"url":"https://bugzilla.suse.com/1264674","tags":["report"]},{"url":"https://bugzilla.suse.com/1264801","tags":["report"]},{"url":"https://bugzilla.suse.com/1264848","tags":["report"]},{"url":"https://bugzilla.suse.com/1265085","tags":["report"]},{"url":"https://bugzilla.suse.com/1265090","tags":["report"]},{"url":"https://bugzilla.suse.com/1265116","tags":["report"]},{"url":"https://bugzilla.suse.com/1265119","tags":["report"]},{"url":"https://bugzilla.suse.com/1265126","tags":["report"]},{"url":"https://bugzilla.suse.com/1265144","tags":["report"]},{"url":"https://bugzilla.suse.com/1265421","tags":["report"]},{"url":"https://bugzilla.suse.com/1265449","tags":["report"]},{"url":"https://bugzilla.suse.com/1265456","tags":["report"]},{"url":"https://bugzilla.suse.com/1265626","tags":["report"]},{"url":"https://bugzilla.suse.com/1265846","tags":["report"]},{"url":"https://bugzilla.suse.com/1265960","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-20585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43009","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43503","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20262238-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1264013","tags":["report"]},{"url":"https://bugzilla.suse.com/1265209","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-54518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46331","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-23343","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23343","tags":["report"]},{"url":"https://git.kernel.org/linus/8821e857759be9db3cde337ad328b71fe5c8a55f","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8567-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8596-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8606-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8607-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8608-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8609-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8619-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8665-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-21709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-62626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64587","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23343","title":"xdp: produce a warning when calculated tailroom is negative","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T10:27:31.13Z","modified":"2026-11-10T12:42:38.108Z","updated_at":"2026-11-10T13:38:44.039016Z"}],"euvd":[{"id":"EUVD-2026-15310","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T10:27:31Z","modified":"2026-11-10T12:42:38Z","updated_at":"2026-11-10T14:21:11.138259Z"}],"ghsa":[{"id":"GHSA-rqf2-6q66-wgpp","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T12:30:23Z","modified":"2026-10-15T03:35:24Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T15:13:31.944762Z"}],"nvd":[{"id":"CVE-2026-23343","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T11:16:32.3Z","modified":"2026-11-10T13:18:42.22Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-787"],"updated_at":"2026-11-10T16:19:45.801381Z"}],"osv":[{"id":"BELL-CVE-2026-23343","status":"published","published":"2026-03-26T06:08:25.139687Z","modified":"2026-06-25T07:18:34.892287733Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:23.315185Z"},{"id":"DEBIAN-CVE-2026-23343","description":"In the Linux kernel, the following vulnerability has been resolved:  xdp: produce a warning when calculated tailroom is negative  Many ethernet drivers report xdp Rx queue frag size as being the same as DMA write size. However, the only user of this field, namely bpf_xdp_frags_increase_tail(), clearly expects a truesize.  Such difference leads to unspecific memory corruption issues under certain circumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when running xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses all DMA-writable space in 2 buffers. This would be fine, if only rxq-\u003efrag_size was properly set to 4K, but value of 3K results in a negative tailroom, because there is a non-zero page offset.  We are supposed to return -EINVAL and be done with it in such case, but due to tailroom being stored as an unsigned int, it is reported to be somewhere near UINT_MAX, resulting in a tail being grown, even if the requested offset is too much (it is around 2K in the abovementioned test). This later leads to all kinds of unspecific calltraces.  [ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6 [ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4 [ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000] [ 7340.339230]  in xskxceiver[42b5,400000+69000] [ 7340.340300]  likely on CPU 6 (core 0, socket 6) [ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe [ 7340.340888]  likely on CPU 3 (core 0, socket 3) [ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7 [ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI [ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy) [ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 [ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80 [ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89 [ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202 [ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010 [ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff [ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0 [ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0 [ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500 [ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000 [ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0 [ 7340.421237] PKRU: 55555554 [ 7340.421623] Call Trace: [ 7340.421987]  \u003cTASK\u003e [ 7340.422309]  ? softleaf_from_pte+0x77/0xa0 [ 7340.422855]  swap_pte_batch+0xa7/0x290 [ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270 [ 7340.424102]  zap_pte_range+0x281/0x580 [ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240 [ 7340.425177]  unmap_page_range+0x24d/0x420 [ 7340.425714]  unmap_vmas+0xa1/0x180 [ 7340.426185]  exit_mmap+0xe1/0x3b0 [ 7340.426644]  __mmput+0x41/0x150 [ 7340.427098]  exit_mm+0xb1/0x110 [ 7340.427539]  do_exit+0x1b2/0x460 [ 7340.427992]  do_group_exit+0x2d/0xc0 [ 7340.428477]  get_signal+0x79d/0x7e0 [ 7340.428957]  arch_do_signal_or_restart+0x34/0x100 [ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0 [ 7340.430159]  do_syscall_64+0x188/ ---truncated---","status":"published","published":"2026-03-25T11:16:32.3Z","modified":"2026-11-06T10:04:04.444573862Z","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-06T10:38:22.758306Z"},{"id":"OESA-2026-1862","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\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:52Z","modified":"2026-08-18T01:19:47.332682492Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"OESA-2026-1863","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\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, a security vulnerability exists in the IOMMU Shared Virtual Addressing (SVA) feature. On x86 architecture when CONFIG_X86 is set, IOMMU hardware caches kernel page table entries. Due to the lack of notification mechanism for kernel page table changes, when kernel page table pages are freed and reused, the IOMMU may retain stale entries, leading to Use-After-Free (UAF) and Write-After-Free (WAF) conditions. This can be exploited to cause arbitrary physical memory DMA access or privilege escalation.(CVE-2025-71089)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix cdev handling in the cleanup path\n\nWhen cdev_device_add fails, it internally releases the cdev memory,\nand if cdev_device_del is then executed, it will cause a hang error.\nTo fix it, we check the return value of cdev_device_add() and clear\nuacce-\u0026gt;cdev to avoid calling cdev_device_del in the uacce_remove.(CVE-2026-23096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: fix use-after-free due to enslave fail after slave array update\n\nFix a use-after-free which happens due to enslave failure after the new\nslave has been added to the array. Since the new slave can be used for Tx\nimmediately, we can use it after it has been freed by the enslave error\ncleanup path which frees the allocated slave memory. Slave update array is\nsupposed to be called last when further enslave failures are not expected.\nMove it after xdp setup to avoid any problems.\n\nIt is very easy to reproduce the problem with a simple xdp_pass prog:\n ip l add bond1 type bond mode balance-xor\n ip l set bond1 up\n ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass\n ip l add dumdum type dummy\n\nThen run in parallel:\n while :; do ip l set dumdum master bond1 1\u0026gt;/dev/null 2\u0026gt;\u0026amp;1; done;\n mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp \u0026quot;dp=1-1023, flags=syn\u0026quot;\n\nThe crash happens almost immediately:\n [  605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI\n [  605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf]\n [  605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G    B               6.19.0-rc6+ #21 PREEMPT(voluntary)\n [  605.602979] Tainted: [B]=BAD_PAGE\n [  605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n [  605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210\n [  605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 \u0026lt;80\u0026gt; 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89\n [  605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213\n [  605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000\n [  605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be\n [  605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c\n [  605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000\n [  605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84\n [  605.603286] FS:  00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000\n [  605.603319] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [  605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0\n [  605.603373] Call Trace:\n [  605.603392]  \u0026lt;TASK\u0026gt;\n [  605.603410]  __dev_queue_xmit+0x448/0x32a0\n [  605.603434]  ? __pfx_vprintk_emit+0x10/0x10\n [  605.603461]  ? __pfx_vprintk_emit+0x10/0x10\n [  605.603484]  ? __pfx___dev_queue_xmit+0x10/0x10\n [  605.603507]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603546]  ? _printk+0xcb/0x100\n [  605.603566]  ? __pfx__printk+0x10/0x10\n [  605.603589]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603627]  ? add_taint+0x5e/0x70\n [  605.603648]  ? add_taint+0x2a/0x70\n [  605.603670]  ? end_report.cold+0x51/0x75\n [  605.603693]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n [  605.603731]  bond_start_xmit+0x623/0xc20 [bonding](CVE-2026-23171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:52Z","modified":"2026-08-18T01:19:47.495909169Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"OESA-2026-1864","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\nf2fs: fix to detect potential corrupted nid in free_nid_list\n\nAs reported, on-disk footer.ino and footer.nid is the same and\nout-of-range, let\u0026apos;s add sanity check on f2fs_alloc_nid() to detect\nany potential corruption in free_nid_list.(CVE-2025-68315)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to \u0026apos;de\u0026apos;; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix use-after-free in nf_tables_addchain()\n\nnf_tables_addchain() publishes the chain to table-\u0026gt;chains via\nlist_add_tail_rcu() (in nft_chain_add()) before registering hooks.\nIf nf_tables_register_hook() then fails, the error path calls\nnft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()\nwith no RCU grace period in between.\n\nThis creates two use-after-free conditions:\n\n 1) Control-plane: nf_tables_dump_chains() traverses table-\u0026gt;chains\n    under rcu_read_lock(). A concurrent dump can still be walking\n    the chain when the error path frees it.\n\n 2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly\n    installs the IPv4 hook before IPv6 registration fails.  Packets\n    entering nft_do_chain() via the transient IPv4 hook can still be\n    dereferencing chain-\u0026gt;blob_gen_X when the error path frees the\n    chain.\n\nAdd synchronize_rcu() between nft_chain_del() and the chain destroy\nso that all RCU readers -- both dump threads and in-flight packet\nevaluation -- have finished before the chain is freed.(CVE-2026-23231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Fix race condition in tls_sw_cancel_work_tx()\n\nThis issue was discovered during a code audit.\n\nAfter cancel_delayed_work_sync() is called from tls_sk_proto_close(),\ntx_work_handler() can still be scheduled from paths such as the\nDelayed ACK handler or ksoftirqd.\nAs a result, the tx_work_handler() worker may dereference a freed\nTLS object.\n\nThe following is a simple race scenario:\n\n          cpu0                         cpu1\n\ntls_sk_proto_close()\n  tls_sw_cancel_work_tx()\n                                 tls_write_space()\n                                   tls_sw_write_space()\n                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, \u0026amp;tx_ctx-\u0026gt;tx_bitmask))\n    set_bit(BIT_TX_SCHEDULED, \u0026amp;ctx-\u0026gt;tx_bitmask);\n    cancel_delayed_work_sync(\u0026amp;ctx-\u0026gt;tx_work.work);\n                                     schedule_delayed_work(\u0026amp;tx_ctx-\u0026gt;tx_work.work, 0);\n\nTo prevent this race condition, cancel_delayed_work_sync() is\nreplaced with disable_delayed_work_sync().(CVE-2026-23240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_gate: snapshot parameters with RCU on replace\n\nThe gate action can be replaced while the hrtimer callback or dump path is\nwalking the schedule list.\n\nConvert the parameters to an RCU-protected snapshot and swap updates under\ntcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits\nthe entry list, preserve the existing schedule so the effective state is\nunchanged.(CVE-2026-23245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix outer network offset\n\nThe udp GRO complete stage assumes that all the packets inserted the RX\nhave the `encapsulation` flag zeroed. Such assumption is not true, as a\nfew H/W NICs can set such flag when H/W offloading the checksum for\nan UDP encapsulated traffic, the tun driver can inject GSO packets with\nUDP encapsulation and the problematic layout can also be created via\na veth based setup.\n\nDue to the above, in the problematic scenarios, udp4_gro_complete() uses\nthe wrong network offset (inner instead of outer) to compute the outer\nUDP header pseudo checksum, leading to csum validation errors later on\nin packet processing.\n\nAddress the issue always clearing the encapsulation flag at GRO completion\ntime. Such flag will be set again as needed for encapsulated packets by\nudp_gro_complete().(CVE-2026-23254)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add proper RCU protection to /proc/net/ptype\n\nYin Fengwei reported an RCU stall in ptype_seq_show() and provided\na patch.\n\nReal issue is that ptype_seq_next() and ptype_seq_show() violate\nRCU rules.\n\nptype_seq_show() runs under rcu_read_lock(), and reads pt-\u0026gt;dev\nto get device name without any barrier.\n\nAt the same time, concurrent writers can remove a packet_type structure\n(which is correctly freed after an RCU grace period) and clear pt-\u0026gt;dev\nwithout an RCU grace period.\n\nDefine ptype_iter_state to carry a dev pointer along seq_net_private:\n\nstruct ptype_iter_state {\n\tstruct seq_net_private\tp;\n\tstruct net_device\t*dev; // added in this patch\n};\n\nWe need to record the device pointer in ptype_get_idx() and\nptype_seq_next() so that ptype_seq_show() is safe against\nconcurrent pt-\u0026gt;dev changes.\n\nWe also need to add full RCU protection in ptype_seq_next().\n(Missing READ_ONCE() when reading list.next values)\n\nMany thanks to Dong Chenchen for providing a repro.(CVE-2026-23255)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks\n\nAs Paolo said earlier [1]:\n\n\u0026quot;Since the blamed commit below, classify can return TC_ACT_CONSUMED while\nthe current skb being held by the defragmentation engine. As reported by\nGangMin Kim, if such packet is that may cause a UaF when the defrag engine\nlater on tries to tuch again such packet.\u0026quot;\n\nact_ct was never meant to be used in the egress path, however some users\nare attaching it to egress today [2]. Attempting to reach a middle\nground, we noticed that, while most qdiscs are not handling\nTC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we\naddress the issue by only allowing act_ct to bind to clsact/ingress\nqdiscs and shared blocks. That way it\u0026apos;s still possible to attach act_ct to\negress (albeit only with clsact).\n\n[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/\n[2] https://lore.kernel.org/netdev/(CVE-2026-23270)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels\n\nIDLETIMER revision 0 rules reuse existing timers by label and always call\nmod_timer() on timer-\u0026gt;timer.\n\nIf the label was created first by revision 1 with XT_IDLETIMER_ALARM,\nthe object uses alarm timer semantics and timer-\u0026gt;timer is never initialized.\nReusing that object from revision 0 causes mod_timer() on an uninitialized\ntimer_list, triggering debugobjects warnings and possible panic when\npanic_on_warn=1.\n\nFix this by rejecting revision 0 rule insertion when an existing timer with\nthe same label is of ALARM type.(CVE-2026-23274)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: add xmit recursion limit to tunnel xmit functions\n\nTunnel xmit functions (iptunnel_xmit, ip6tunnel_xmit) lack their own\nrecursion limit. When a bond device in broadcast mode has GRE tap\ninterfaces as slaves, and those GRE tunnels route back through the\nbond, multicast/broadcast traffic triggers infinite recursion between\nbond_xmit_broadcast() and ip_tunnel_xmit()/ip6_tnl_xmit(), causing\nkernel stack overflow.\n\nThe existing XMIT_RECURSION_LIMIT (8) in the no-qdisc path is not\nsufficient because tunnel recursion involves route lookups and full IP\noutput, consuming much more stack per level. Use a lower limit of 4\n(IP_TUNNEL_RECURSION_LIMIT) to prevent overflow.\n\nAdd recursion detection using dev_xmit_recursion helpers directly in\niptunnel_xmit() and ip6tunnel_xmit() to cover all IPv4/IPv6 tunnel\npaths including UDP encapsulated tunnels (VXLAN, Geneve, etc.).\n\nMove dev_xmit_recursion helpers from net/core/dev.h to public header\ninclude/linux/netdevice.h so they can be used by tunnel code.\n\n BUG: KASAN: stack-out-of-bounds in blake2s.constprop.0+0xe7/0x160\n Write of size 32 at addr ffff88810033fed0 by task kworker/0:1/11\n Workqueue: mld mld_ifc_work\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __build_flow_key.constprop.0 (net/ipv4/route.c:515)\n  ip_rt_update_pmtu (net/ipv4/route.c:1073)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:84)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  ip_output (net/ipv4/ip_output.c:438)\n  iptunnel_xmit (net/ipv4/ip_tunnel_core.c:86)\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  bond_dev_queue_xmit (drivers/net/bonding/bond_main.c:312)\n  bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5279)\n  bond_start_xmit (drivers/net/bonding/bond_main.c:5530)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  __dev_queue_xmit (net/core/dev.c:4841)\n  mld_sendpack\n  mld_ifc_work\n  process_one_work\n  worker_thread\n  \u0026lt;/TASK\u0026gt;(CVE-2026-23276)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit\n\nteql_master_xmit() calls netdev_start_xmit(skb, slave) to transmit\nthrough slave devices, but does not update skb-\u0026gt;dev to the slave device\nbeforehand.\n\nWhen a gretap tunnel is a TEQL slave, the transmit path reaches\niptunnel_xmit() which saves dev = skb-\u0026gt;dev (still pointing to teql0\nmaster) and later calls iptunnel_xmit_stats(dev, pkt_len). This\nfunction does:\n\n    get_cpu_ptr(dev-\u0026gt;tstats)\n\nSince teql_master_setup() does not set dev-\u0026gt;pcpu_stat_type to\nNETDEV_PCPU_STAT_TSTATS, the core network stack never allocates tstats\nfor teql0, so dev-\u0026gt;tstats is NULL. get_cpu_ptr(NULL) computes\nNULL + __per_cpu_offset[cpu], resulting in a page fault.\n\n BUG: unable to handle page fault for address: ffff8880e6659018\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 68bc067 P4D 68bc067 PUD 0\n Oops: Oops: 0002 [#1] SMP KASAN PTI\n RIP: 0010:iptunnel_xmit (./include/net/ip_tunnels.h:664 net/ipv4/ip_tunnel_core.c:89)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  ip_tunnel_xmit (net/ipv4/ip_tunnel.c:847)\n  __gre_xmit (net/ipv4/ip_gre.c:478)\n  gre_tap_xmit (net/ipv4/ip_gre.c:779)\n  teql_master_xmit (net/sched/sch_teql.c:319)\n  dev_hard_start_xmit (net/core/dev.c:3887)\n  sch_direct_xmit (net/sched/sch_generic.c:347)\n  __dev_queue_xmit (net/core/dev.c:4802)\n  neigh_direct_output (net/core/neighbour.c:1660)\n  ip_finish_output2 (net/ipv4/ip_output.c:237)\n  __ip_finish_output.part.0 (net/ipv4/ip_output.c:315)\n  ip_mc_output (net/ipv4/ip_output.c:369)\n  ip_send_skb (net/ipv4/ip_output.c:1508)\n  udp_send_skb (net/ipv4/udp.c:1195)\n  udp_sendmsg (net/ipv4/udp.c:1485)\n  inet_sendmsg (net/ipv4/af_inet.c:859)\n  __sys_sendto (net/socket.c:2206)\n\nFix this by setting skb-\u0026gt;dev = slave before calling\nnetdev_start_xmit(), so that tunnel xmit functions see the correct\nslave device with properly allocated tstats.(CVE-2026-23277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: always walk all pending catchall elements\n\nDuring transaction processing we might have more than one catchall element:\n1 live catchall element and 1 pending element that is coming as part of the\nnew batch.\n\nIf the map holding the catchall elements is also going away, its\nrequired to toggle all catchall elements and not just the first viable\ncandidate.\n\nOtherwise, we get:\n WARNING: ./include/net/netfilter/nf_tables.h:1281 at nft_data_release+0xb7/0xe0 [nf_tables], CPU#2: nft/1404\n RIP: 0010:nft_data_release+0xb7/0xe0 [nf_tables]\n [..]\n __nft_set_elem_destroy+0x106/0x380 [nf_tables]\n nf_tables_abort_release+0x348/0x8d0 [nf_tables]\n nf_tables_abort+0xcf2/0x3ac0 [nf_tables]\n nfnetlink_rcv_batch+0x9c9/0x20e0 [..](CVE-2026-23278)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. If an IPv6 packet is injected into the interface,\nroute_shortcircuit() is called and a NULL pointer dereference happens on\nneigh_lookup().\n\n BUG: kernel NULL pointer dereference, address: 0000000000000380\n Oops: Oops: 0000 [#1] SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x20/0x270\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  vxlan_xmit+0x638/0x1ef0 [vxlan]\n  dev_hard_start_xmit+0x9e/0x2e0\n  __dev_queue_xmit+0xbee/0x14e0\n  packet_sendmsg+0x116f/0x1930\n  __sys_sendto+0x1f5/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x12f/0x1590\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nFix this by adding an early check on route_shortcircuit() when protocol\nis ETH_P_IPV6. Note that ipv6_mod_enabled() cannot be used here because\nVXLAN can be built-in even when IPv6 is built as a module.(CVE-2026-23293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop\n\nWhen a standalone IPv6 nexthop object is created with a loopback device\n(e.g., \u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;), fib6_nh_init() misclassifies\nit as a reject route. This is because nexthop objects have no destination\nprefix (fc_dst=::), causing fib6_is_reject() to match any loopback\nnexthop. The reject path skips fib_nh_common_init(), leaving\nnhc_pcpu_rth_output unallocated. If an IPv4 route later references this\nnexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and\npanics.\n\nSimplify the check in fib6_nh_init() to only match explicit reject\nroutes (RTF_REJECT) instead of using fib6_is_reject(). The loopback\npromotion heuristic in fib6_is_reject() is handled separately by\nip6_route_info_create_nh(). After this change, the three cases behave\nas follows:\n\n1. Explicit reject route (\u0026quot;ip -6 route add unreachable 2001:db8::/64\u0026quot;):\n   RTF_REJECT is set, enters reject path, skips fib_nh_common_init().\n   No behavior change.\n\n2. Implicit loopback reject route (\u0026quot;ip -6 route add 2001:db8::/32 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. ip6_route_info_create_nh() still promotes it to reject\n   afterward. nhc_pcpu_rth_output is allocated but unused, which is\n   harmless.\n\n3. Standalone nexthop object (\u0026quot;ip -6 nexthop add id 100 dev lo\u0026quot;):\n   RTF_REJECT is not set, takes normal path, fib_nh_common_init() is\n   called. nhc_pcpu_rth_output is properly allocated, fixing the crash\n   when IPv4 routes reference this nexthop.(CVE-2026-23300)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: annotate data-races around sk-\u0026gt;sk_{data_ready,write_space}\n\nskmsg (and probably other layers) are changing these pointers\nwhile other cpus might read them concurrently.\n\nAdd corresponding READ_ONCE()/WRITE_ONCE() annotations\nfor UDP, TCP and AF_UNIX.(CVE-2026-23302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Don\u0026apos;t log plaintext credentials in cifs_set_cifscreds\n\nWhen debug logging is enabled, cifs_set_cifscreds() logs the key\npayload and exposes the plaintext username and password. Remove the\ndebug log to avoid exposing credentials.(CVE-2026-23303)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()\n\nl3mdev_master_dev_rcu() can return NULL when the slave device is being\nun-slaved from a VRF. All other callers deal with this, but we lost\nthe fallback to loopback in ip6_rt_pcpu_alloc() -\u0026gt; ip6_rt_get_dev_rcu()\nwith commit 4832c30d5458 (\u0026quot;net: ipv6: put host and anycast routes on\ndevice with address\u0026quot;).\n\n  KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n  RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)\n  Call Trace:\n   ip6_pol_route (net/ipv6/route.c:2318)\n   fib6_rule_lookup (net/ipv6/fib6_rules.c:115)\n   ip6_route_output_flags (net/ipv6/route.c:2607)\n   vrf_process_v6_outbound (drivers/net/vrf.c:437)\n\nI was tempted to rework the un-slaving code to clear the flag first\nand insert synchronize_rcu() before we remove the upper. But looks like\nthe explicit fallback to loopback_dev is an established pattern.\nAnd I guess avoiding the synchronize_rcu() is nice, too.(CVE-2026-23304)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded\n\nbond_option_mode_set() already rejects mode changes that would make a\nloaded XDP program incompatible via bond_xdp_check().  However,\nbond_option_xmit_hash_policy_set() has no such guard.\n\nFor 802.3ad and balance-xor modes, bond_xdp_check() returns false when\nxmit_hash_policy is vlan+srcmac, because the 802.1q payload is usually\nabsent due to hardware offload.  This means a user can:\n\n1. Attach a native XDP program to a bond in 802.3ad/balance-xor mode\n   with a compatible xmit_hash_policy (e.g. layer2+3).\n2. Change xmit_hash_policy to vlan+srcmac while XDP remains loaded.\n\nThis leaves bond-\u0026gt;xdp_prog set but bond_xdp_check() now returning false\nfor the same device.  When the bond is later destroyed, dev_xdp_uninstall()\ncalls bond_xdp_set(dev, NULL, NULL) to remove the program, which hits\nthe bond_xdp_check() guard and returns -EOPNOTSUPP, triggering:\n\nWARN_ON(dev_xdp_install(dev, mode, bpf_op, NULL, 0, NULL))\n\nFix this by rejecting xmit_hash_policy changes to vlan+srcmac when an\nXDP program is loaded on a bond in 802.3ad or balance-xor mode.\n\ncommit 39a0876d595b (\u0026quot;net, bonding: Disallow vlan+srcmac with XDP\u0026quot;)\nintroduced bond_xdp_check() which returns false for 802.3ad/balance-xor\nmodes when xmit_hash_policy is vlan+srcmac.  The check was wired into\nbond_xdp_set() to reject XDP attachment with an incompatible policy, but\nthe symmetric path -- preventing xmit_hash_policy from being changed to an\nincompatible value after XDP is already loaded -- was left unguarded in\nbond_option_xmit_hash_policy_set().\n\nNote:\ncommit 094ee6017ea0 (\u0026quot;bonding: check xdp prog when set bond mode\u0026quot;)\nlater added a similar guard to bond_option_mode_set(), but\nbond_option_xmit_hash_policy_set() remained unprotected.(CVE-2026-23310)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: in-kernel: always mark signal+subflow endp as used\n\nSyzkaller managed to find a combination of actions that was generating\nthis warning:\n\n  msk-\u0026gt;pm.local_addr_used == 0\n  WARNING: net/mptcp/pm_kernel.c:1071 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline], CPU#1: syz.2.17/961\n  WARNING: net/mptcp/pm_kernel.c:1071 at mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210, CPU#1: syz.2.17/961\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 961 Comm: syz.2.17 Not tainted 6.19.0-08368-gfafda3b4b06b #22 PREEMPT(full)\n  Hardware name: QEMU Ubuntu 25.10 PC v2 (i440FX + PIIX, + 10.1 machine, 1996), BIOS 1.17.0-debian-1.17.0-1build1 04/01/2014\n  RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1071 [inline]\n  RIP: 0010:mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_kernel.c:1103 [inline]\n  RIP: 0010:mptcp_pm_nl_del_addr_doit+0x81d/0x8f0 net/mptcp/pm_kernel.c:1210\n  Code: 89 c5 e8 46 30 6f fe e9 21 fd ff ff 49 83 ed 80 e8 38 30 6f fe 4c 89 ef be 03 00 00 00 e8 db 49 df fe eb ac e8 24 30 6f fe 90 \u0026lt;0f\u0026gt; 0b 90 e9 1d ff ff ff e8 16 30 6f fe eb 05 e8 0f 30 6f fe e8 9a\n  RSP: 0018:ffffc90001663880 EFLAGS: 00010293\n  RAX: ffffffff82de1a6c RBX: 0000000000000000 RCX: ffff88800722b500\n  RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n  RBP: ffff8880158b22d0 R08: 0000000000010425 R09: ffffffffffffffff\n  R10: ffffffff82de18ba R11: 0000000000000000 R12: ffff88800641a640\n  R13: ffff8880158b1880 R14: ffff88801ec3c900 R15: ffff88800641a650\n  FS:  00005555722c3500(0000) GS:ffff8880f909d000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00007f66346e0f60 CR3: 000000001607c000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115\n   genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n   genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210\n   netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550\n   genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n   netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n   netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344\n   netlink_sendmsg+0x4aa/0x5b0 net/netlink/af_netlink.c:1894\n   sock_sendmsg_nosec net/socket.c:727 [inline]\n   __sock_sendmsg+0xc9/0xf0 net/socket.c:742\n   ____sys_sendmsg+0x272/0x3b0 net/socket.c:2592\n   ___sys_sendmsg+0x2de/0x320 net/socket.c:2646\n   __sys_sendmsg net/socket.c:2678 [inline]\n   __do_sys_sendmsg net/socket.c:2683 [inline]\n   __se_sys_sendmsg net/socket.c:2681 [inline]\n   __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2681\n   do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0x143/0x440 arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  RIP: 0033:0x7f66346f826d\n  Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 e8 ff ff ff f7 d8 64 89 01 48\n  RSP: 002b:00007ffc83d8bdc8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n  RAX: ffffffffffffffda RBX: 00007f6634985fa0 RCX: 00007f66346f826d\n  RDX: 00000000040000b0 RSI: 0000200000000740 RDI: 0000000000000007\n  RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6634985fa8\n  R13: 00007f6634985fac R14: 0000000000000000 R15: 0000000000001770\n   \u0026lt;/TASK\u0026gt;\n\nThe actions that caused that seem to be:\n\n - Set the MPTCP subflows limit to 0\n - Create an MPTCP endpoint with both the \u0026apos;signal\u0026apos; and \u0026apos;subflow\u0026apos; flags\n - Create a new MPTCP connection from a different address: an ADD_ADDR\n   linked to the MPTCP endpoint will be sent (\u0026apos;signal\u0026apos; flag), but no\n   subflows is initiated (\u0026apos;subflow\u0026apos; flag)\n - Remove the MPTCP endpoint\n\n---truncated---(CVE-2026-23321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver\u0026apos;s XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u0026gt;frag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u0026lt;4c\u0026gt; 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u0026lt;8b\u0026gt; 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u0026lt;8b\u0026gt; 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u0026lt;TASK\u0026gt;\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---(CVE-2026-23343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_set_pipapo: split gc into unlink and reclaim phase\n\nYiming Qian reports Use-after-free in the pipapo set type:\n  Under a large number of expired elements, commit-time GC can run for a very\n  long time in a non-preemptible context, triggering soft lockup warnings and\n  RCU stall reports (local denial of service).\n\nWe must split GC in an unlink and a reclaim phase.\n\nWe cannot queue elements for freeing until pointers have been swapped.\nExpired elements are still exposed to both the packet path and userspace\ndumpers via the live copy of the data structure.\n\ncall_rcu() does not protect us: dump operations or element lookups starting\nafter call_rcu has fired can still observe the free\u0026apos;d element, unless the\ncommit phase has made enough progress to swap the clone and live pointers\nbefore any new reader has picked up the old version.\n\nThis a similar approach as done recently for the rbtree backend in commit\n35f83a75529a (\u0026quot;netfilter: nft_set_rbtree: don\u0026apos;t gc elements on insert\u0026quot;).(CVE-2026-23351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: fix locking for bcm_op runtime updates\n\nCommit c2aba69d0c36 (\u0026quot;can: bcm: add locking for bcm_op runtime updates\u0026quot;)\nadded a locking for some variables that can be modified at runtime when\nupdating the sending bcm_op with a new TX_SETUP command in bcm_tx_setup().\n\nUsually the RX_SETUP only handles and filters incoming traffic with one\nexception: When the RX_RTR_FRAME flag is set a predefined CAN frame is\nsent when a specific RTR frame is received. Therefore the rx bcm_op uses\nbcm_can_tx() which uses the bcm_tx_lock that was only initialized in\nbcm_tx_setup(). Add the missing spin_lock_init() when allocating the\nbcm_op in bcm_rx_setup() to handle the RTR case properly.(CVE-2026-23362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kalmia: validate USB endpoints\n\nThe kalmia driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23365)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: phy: register phy led_triggers during probe to avoid AB-BA deadlock\n\nThere is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and\nLED_TRIGGER_PHY are enabled:\n\n[ 1362.049207] [\u0026lt;8054e4b8\u0026gt;] led_trigger_register+0x5c/0x1fc             \u0026lt;-- Trying to get lock \u0026quot;triggers_list_lock\u0026quot; via down_write(\u0026amp;triggers_list_lock);\n[ 1362.054536] [\u0026lt;80662830\u0026gt;] phy_led_triggers_register+0xd0/0x234\n[ 1362.060329] [\u0026lt;8065e200\u0026gt;] phy_attach_direct+0x33c/0x40c\n[ 1362.065489] [\u0026lt;80651fc4\u0026gt;] phylink_fwnode_phy_connect+0x15c/0x23c\n[ 1362.071480] [\u0026lt;8066ee18\u0026gt;] mtk_open+0x7c/0xba0\n[ 1362.075849] [\u0026lt;806d714c\u0026gt;] __dev_open+0x280/0x2b0\n[ 1362.080384] [\u0026lt;806d7668\u0026gt;] __dev_change_flags+0x244/0x24c\n[ 1362.085598] [\u0026lt;806d7698\u0026gt;] dev_change_flags+0x28/0x78\n[ 1362.090528] [\u0026lt;807150e4\u0026gt;] dev_ioctl+0x4c0/0x654                       \u0026lt;-- Hold lock \u0026quot;rtnl_mutex\u0026quot; by calling rtnl_lock();\n[ 1362.094985] [\u0026lt;80694360\u0026gt;] sock_ioctl+0x2f4/0x4e0\n[ 1362.099567] [\u0026lt;802e9c4c\u0026gt;] sys_ioctl+0x32c/0xd8c\n[ 1362.104022] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LED_TRIGGER_PHY is registering LED triggers during phy_attach\nwhile holding RTNL and then taking triggers_list_lock.\n\n[ 1362.191101] [\u0026lt;806c2640\u0026gt;] register_netdevice_notifier+0x60/0x168      \u0026lt;-- Trying to get lock \u0026quot;rtnl_mutex\u0026quot; via rtnl_lock();\n[ 1362.197073] [\u0026lt;805504ac\u0026gt;] netdev_trig_activate+0x194/0x1e4\n[ 1362.202490] [\u0026lt;8054e28c\u0026gt;] led_trigger_set+0x1d4/0x360                 \u0026lt;-- Hold lock \u0026quot;triggers_list_lock\u0026quot; by down_read(\u0026amp;triggers_list_lock);\n[ 1362.207511] [\u0026lt;8054eb38\u0026gt;] led_trigger_write+0xd8/0x14c\n[ 1362.212566] [\u0026lt;80381d98\u0026gt;] sysfs_kf_bin_write+0x80/0xbc\n[ 1362.217688] [\u0026lt;8037fcd8\u0026gt;] kernfs_fop_write_iter+0x17c/0x28c\n[ 1362.223174] [\u0026lt;802cbd70\u0026gt;] vfs_write+0x21c/0x3c4\n[ 1362.227712] [\u0026lt;802cc0c4\u0026gt;] ksys_write+0x78/0x12c\n[ 1362.232164] [\u0026lt;80014504\u0026gt;] syscall_common+0x34/0x58\n\nHere LEDS_TRIGGER_NETDEV is being enabled on an LED. It first takes\ntriggers_list_lock and then RTNL. A classical AB-BA deadlock.\n\nphy_led_triggers_registers() does not require the RTNL, it does not\nmake any calls into the network stack which require protection. There\nis also no requirement the PHY has been attached to a MAC, the\ntriggers only make use of phydev state. This allows the call to\nphy_led_triggers_registers() to be placed elsewhere. PHY probe() and\nrelease() don\u0026apos;t hold RTNL, so solving the AB-BA deadlock.(CVE-2026-23368)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting\n\nRunning stress-ng --schedpolicy 0 on an RT kernel on a big machine\nmight lead to the following WARNINGs (edited).\n\n sched: DL de-boosted task PID 22725: REPLENISH flag missing\n\n WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8\n ... (running_bw underflow)\n Call trace:\n  dequeue_task_dl+0x15c/0x1f8 (P)\n  dequeue_task+0x80/0x168\n  deactivate_task+0x24/0x50\n  push_dl_task+0x264/0x2e0\n  dl_task_timer+0x1b0/0x228\n  __hrtimer_run_queues+0x188/0x378\n  hrtimer_interrupt+0xfc/0x260\n  ...\n\nThe problem is that when a SCHED_DEADLINE task (lock holder) is\nchanged to a lower priority class via sched_setscheduler(), it may\nfail to properly inherit the parameters of potential DEADLINE donors\nif it didn\u0026apos;t already inherit them in the past (shorter deadline than\ndonor\u0026apos;s at that time). This might lead to bandwidth accounting\ncorruption, as enqueue_task_dl() won\u0026apos;t recognize the lock holder as\nboosted.\n\nThe scenario occurs when:\n1. A DEADLINE task (donor) blocks on a PI mutex held by another\n   DEADLINE task (holder), but the holder doesn\u0026apos;t inherit parameters\n   (e.g., it already has a shorter deadline)\n2. sched_setscheduler() changes the holder from DEADLINE to a lower\n   class while still holding the mutex\n3. The holder should now inherit DEADLINE parameters from the donor\n   and be enqueued with ENQUEUE_REPLENISH, but this doesn\u0026apos;t happen\n\nFix the issue by introducing __setscheduler_dl_pi(), which detects when\na DEADLINE (proper or boosted) task gets setscheduled to a lower\npriority class. In case, the function makes the task inherit DEADLINE\nparameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to\nensure proper bandwidth accounting during the next enqueue operation.(CVE-2026-23371)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm: thp: deny THP for files on anonymous inodes\n\nfile_thp_enabled() incorrectly allows THP for files on anonymous inodes\n(e.g. guest_memfd and secretmem). These files are created via\nalloc_file_pseudo(), which does not call get_write_access() and leaves\ninode-\u0026gt;i_writecount at 0. Combined with S_ISREG(inode-\u0026gt;i_mode) being\ntrue, they appear as read-only regular files when\nCONFIG_READ_ONLY_THP_FOR_FS is enabled, making them eligible for THP\ncollapse.\n\nAnonymous inodes can never pass the inode_is_open_for_write() check\nsince their i_writecount is never incremented through the normal VFS\nopen path. The right thing to do is to exclude them from THP eligibility\naltogether, since CONFIG_READ_ONLY_THP_FOR_FS was designed for real\nfilesystem files (e.g. shared libraries), not for pseudo-filesystem\ninodes.\n\nFor guest_memfd, this allows khugepaged and MADV_COLLAPSE to create\nlarge folios in the page cache via the collapse path, but the\nguest_memfd fault handler does not support large folios. This triggers\nWARN_ON_ONCE(folio_test_large(folio)) in kvm_gmem_fault_user_mapping().\n\nFor secretmem, collapse_file() tries to copy page contents through the\ndirect map, but secretmem pages are removed from the direct map. This\ncan result in a kernel crash:\n\n    BUG: unable to handle page fault for address: ffff88810284d000\n    RIP: 0010:memcpy_orig+0x16/0x130\n    Call Trace:\n     collapse_file\n     hpage_collapse_scan_file\n     madvise_collapse\n\nSecretmem is not affected by the crash on upstream as the memory failure\nrecovery handles the failed copy gracefully, but it still triggers\nconfusing false memory failure reports:\n\n    Memory failure: 0x106d96f: recovery action for clean unevictable\n    LRU page: Recovered\n\nCheck IS_ANON_FILE(inode) in file_thp_enabled() to deny THP for all\nanonymous inode files.(CVE-2026-23375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: fix nd_tbl NULL dereference when IPv6 is disabled\n\nWhen booting with the \u0026apos;ipv6.disable=1\u0026apos; parameter, the nd_tbl is never\ninitialized because inet6_init() exits before ndisc_init() is called\nwhich initializes it. Then, if neigh_suppress is enabled and an ICMPv6\nNeighbor Discovery packet reaches the bridge, br_do_suppress_nd() will\ndereference ipv6_stub-\u0026gt;nd_tbl which is NULL, passing it to\nneigh_lookup(). This causes a kernel NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000268\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n [...]\n RIP: 0010:neigh_lookup+0x16/0xe0\n [...]\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  ? neigh_lookup+0x16/0xe0\n  br_do_suppress_nd+0x160/0x290 [bridge]\n  br_handle_frame_finish+0x500/0x620 [bridge]\n  br_handle_frame+0x353/0x440 [bridge]\n  __netif_receive_skb_core.constprop.0+0x298/0x1110\n  __netif_receive_skb_one_core+0x3d/0xa0\n  process_backlog+0xa0/0x140\n  __napi_poll+0x2c/0x170\n  net_rx_action+0x2c4/0x3a0\n  handle_softirqs+0xd0/0x270\n  do_softirq+0x3f/0x60\n\nFix this by replacing IS_ENABLED(IPV6) call with ipv6_mod_enabled() in\nthe callers. This is in essence disabling NS/NA suppression when IPv6 is\ndisabled.(CVE-2026-23381)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: xt_CT: drop pending enqueued packets on template removal\n\nTemplates refer to objects that can go away while packets are sitting in\nnfqueue refer to:\n\n- helper, this can be an issue on module removal.\n- timeout policy, nfnetlink_cttimeout might remove it.\n\nThe use of templates with zone and event cache filter are safe, since\nthis just copies values.\n\nFlush these enqueued packets in case the template rule gets removed.(CVE-2026-23391)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: release flowtable after rcu grace period on error\n\nCall synchronize_rcu() after unregistering the hooks from error path,\nsince a hook that already refers to this flowtable can be already\nregistered, exposing this flowtable to packet path and nfnetlink_hook\ncontrol plane.\n\nThis error path is rare, it should only happen by reaching the maximum\nnumber hooks or by failing to set up to hardware offload, just call\nsynchronize_rcu().\n\nThere is a check for already used device hooks by different flowtable\nthat could result in EEXIST at this late stage. The hook parser can be\nupdated to perform this check earlier to this error path really becomes\nrarely exercised.\n\nUncovered by KASAN reported as use-after-free from nfnetlink_hook path\nwhen dumping hooks.(CVE-2026-23392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: cfm: Fix race condition in peer_mep deletion\n\nWhen a peer MEP is being deleted, cancel_delayed_work_sync() is called\non ccm_rx_dwork before freeing. However, br_cfm_frame_rx() runs in\nsoftirq context under rcu_read_lock (without RTNL) and can re-schedule\nccm_rx_dwork via ccm_rx_timer_start() between cancel_delayed_work_sync()\nreturning and kfree_rcu() being called.\n\nThe following is a simple race scenario:\n\n           cpu0                                     cpu1\n\nmep_delete_implementation()\n  cancel_delayed_work_sync(ccm_rx_dwork);\n                                           br_cfm_frame_rx()\n                                             // peer_mep still in hlist\n                                             if (peer_mep-\u0026gt;ccm_defect)\n                                               ccm_rx_timer_start()\n                                                 queue_delayed_work(ccm_rx_dwork)\n  hlist_del_rcu(\u0026amp;peer_mep-\u0026gt;head);\n  kfree_rcu(peer_mep, rcu);\n                                           ccm_rx_work_expired()\n                                             // on freed peer_mep\n\nTo prevent this, cancel_delayed_work_sync() is replaced with\ndisable_delayed_work_sync() in both peer MEP deletion paths, so\nthat subsequent queue_delayed_work() calls from br_cfm_frame_rx()\nare silently rejected.\n\nThe cc_peer_disable() helper retains cancel_delayed_work_sync()\nbecause it is also used for the CC enable/disable toggle path where\nthe work must remain re-schedulable.(CVE-2026-23393)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\u0026quot;af_unix: fix garbage collect vs MSG_PEEK\u0026quot;).\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n  GC thread                    User thread\n  ---------                    -----------\n  unix_vertex_dead(sk-A)\n  -\u0026gt; true   \u0026lt;------.\n                    \\\n                     `------   recv(sk-B, MSG_PEEK)\n              invalidate !!    -\u0026gt; sk-A\u0026apos;s file refcount : 1 -\u0026gt; 2\n\n                               close(sk-B)\n                               -\u0026gt; sk-B\u0026apos;s file refcount : 2 -\u0026gt; 1\n  unix_vertex_dead(sk-B)\n  -\u0026gt; true\n\nInitially, sk-A\u0026apos;s file refcount is 1 by the inflight fd in sk-B\nrecvq.  GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A\u0026apos;s file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B\u0026apos;s file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A.  The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet\u0026apos;s use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.(CVE-2026-23394)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ\n\nCurrently the code attempts to accept requests regardless of the\ncommand identifier which may cause multiple requests to be marked\nas pending (FLAG_DEFER_SETUP) which can cause more than\nL2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer\ncausing an overflow.\n\nThe spec is quite clear that the same identifier shall not be used on\nsubsequent requests:\n\n\u0026apos;Within each signaling channel a different Identifier shall be used\nfor each successive request or indication.\u0026apos;\nhttps://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d\n\nSo this attempts to check if there are any channels pending with the\nsame identifier and rejects if any are found.(CVE-2026-23395)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfnetlink_osf: validate individual option lengths in fingerprints\n\nnfnl_osf_add_callback() validates opt_num bounds and string\nNUL-termination but does not check individual option length fields.\nA zero-length option causes nf_osf_match_one() to enter the option\nmatching loop even when foptsize sums to zero, which matches packets\nwith no TCP options where ctx-\u0026gt;optp is NULL:\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\n RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98)\n Call Trace:\n  nf_osf_match (net/netfilter/nfnetlink_osf.c:227)\n  xt_osf_match_packet (net/netfilter/xt_osf.c:32)\n  ipt_do_table (net/ipv4/netfilter/ip_tables.c:293)\n  nf_hook_slow (net/netfilter/core.c:623)\n  ip_local_deliver (net/ipv4/ip_input.c:262)\n  ip_rcv (net/ipv4/ip_input.c:573)\n\nAdditionally, an MSS option (kind=2) with length \u0026lt; 4 causes\nout-of-bounds reads when nf_osf_match_one() unconditionally accesses\noptp[2] and optp[3] for MSS value extraction.  While RFC 9293\nsection 3.2 specifies that the MSS option is always exactly 4\nbytes (Kind=2, Length=4), the check uses \u0026quot;\u0026lt; 4\u0026quot; rather than\n\u0026quot;!= 4\u0026quot; because lengths greater than 4 do not cause memory\nsafety issues -- the buffer is guaranteed to be at least\nfoptsize bytes by the ctx-\u0026gt;optsize == foptsize check.\n\nReject fingerprints where any option has zero length, or where an MSS\noption has length less than 4, at add time rather than trusting these\nvalues in the packet matching hot path.(CVE-2026-23397)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnf_tables: nft_dynset: fix possible stateful expression memleak in error path\n\nIf cloning the second stateful expression in the element via GFP_ATOMIC\nfails, then the first stateful expression remains in place without being\nreleased.\n\n   unreferenced object (percpu) 0x607b97e9cab8 (size 16):\n     comm \u0026quot;softirq\u0026quot;, pid 0, jiffies 4294931867\n     hex dump (first 16 bytes on cpu 3):\n       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     backtrace (crc 0):\n       pcpu_alloc_noprof+0x453/0xd80\n       nft_counter_clone+0x9c/0x190 [nf_tables]\n       nft_expr_clone+0x8f/0x1b0 [nf_tables]\n       nft_dynset_new+0x2cb/0x5f0 [nf_tables]\n       nft_rhash_update+0x236/0x11c0 [nf_tables]\n       nft_dynset_eval+0x11f/0x670 [nf_tables]\n       nft_do_chain+0x253/0x1700 [nf_tables]\n       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]\n       nf_hook_slow+0xaa/0x1e0\n       ip_local_deliver+0x209/0x330(CVE-2026-23399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE\n\nWhen installing an emulated MMIO SPTE, do so *after* dropping/zapping the\nexisting SPTE (if it\u0026apos;s shadow-present).  While commit a54aa15c6bda3 was\nright about it being impossible to convert a shadow-present SPTE to an\nMMIO SPTE due to a _guest_ write, it failed to account for writes to guest\nmemory that are outside the scope of KVM.\n\nE.g. if host userspace modifies a shadowed gPTE to switch from a memslot\nto emulted MMIO and then the guest hits a relevant page fault, KVM will\ninstall the MMIO SPTE without first zapping the shadow-present SPTE.\n\n  ------------[ cut here ]------------\n  is_shadow_present_pte(*sptep)\n  WARNING: arch/x86/kvm/mmu/mmu.c:484 at mark_mmio_spte+0xb2/0xc0 [kvm], CPU#0: vmx_ept_stale_r/4292\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 0 UID: 1000 PID: 4292 Comm: vmx_ept_stale_r Not tainted 7.0.0-rc2-eafebd2d2ab0-sink-vm #319 PREEMPT\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:mark_mmio_spte+0xb2/0xc0 [kvm]\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   mmu_set_spte+0x237/0x440 [kvm]\n   ept_page_fault+0x535/0x7f0 [kvm]\n   kvm_mmu_do_page_fault+0xee/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8d/0x620 [kvm]\n   vmx_handle_exit+0x18c/0x5a0 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0xc55/0x1c20 [kvm]\n   kvm_vcpu_ioctl+0x2d5/0x980 [kvm]\n   __x64_sys_ioctl+0x8a/0xd0\n   do_syscall_64+0xb5/0x730\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x47fa3f\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---(CVE-2026-23401)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix memory leak in verify_header\n\nThe function sets `*ns = NULL` on every call, leaking the namespace\nstring allocated in previous iterations when multiple profiles are\nunpacked. This also breaks namespace consistency checking since *ns\nis always NULL when the comparison is made.\n\nRemove the incorrect assignment.\nThe caller (aa_unpack) initializes *ns to NULL once before the loop,\nwhich is sufficient.(CVE-2026-23403)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: replace recursive profile removal with iterative approach\n\nThe profile removal code uses recursion when removing nested profiles,\nwhich can lead to kernel stack exhaustion and system crashes.\n\nReproducer:\n  $ pf=\u0026apos;a\u0026apos;; for ((i=0; i\u0026lt;1024; i++)); do\n      echo -e \u0026quot;profile $pf { \\n }\u0026quot; | apparmor_parser -K -a;\n      pf=\u0026quot;$pf//x\u0026quot;;\n  done\n  $ echo -n a \u0026gt; /sys/kernel/security/apparmor/.remove\n\nReplace the recursive __aa_profile_list_release() approach with an\niterative approach in __remove_profile(). The function repeatedly\nfinds and removes leaf profiles until the entire subtree is removed,\nmaintaining the same removal semantic without recursion.(CVE-2026-23404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix: limit the number of levels of policy namespaces\n\nCurrently the number of policy namespaces is not bounded relying on\nthe user namespace limit. However policy namespaces aren\u0026apos;t strictly\ntied to user namespaces and it is possible to create them and nest\nthem arbitrarily deep which can be used to exhaust system resource.\n\nHard cap policy namespaces to the same depth as user namespaces.(CVE-2026-23405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: Fix double free of ns_name in aa_replace_profiles()\n\nif ns_name is NULL after\n1071         error = aa_unpack(udata, \u0026amp;lh, \u0026amp;ns_name);\n\nand if ent-\u0026gt;ns_name contains an ns_name in\n1089                 } else if (ent-\u0026gt;ns_name) {\n\nthen ns_name is assigned the ent-\u0026gt;ns_name\n1095                         ns_name = ent-\u0026gt;ns_name;\n\nhowever ent-\u0026gt;ns_name is freed at\n1262                 aa_load_ent_free(ent);\n\nand then again when freeing ns_name at\n1270         kfree(ns_name);\n\nFix this by NULLing out ent-\u0026gt;ns_name after it is transferred to ns_name\n\n\u0026quot;)(CVE-2026-23408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix differential encoding verification\n\nDifferential encoding allows loops to be created if it is abused. To\nprevent this the unpack should verify that a diff-encode chain\nterminates.\n\nUnfortunately the differential encode verification had two bugs.\n\n1. it conflated states that had gone through check and already been\n   marked, with states that were currently being checked and marked.\n   This means that loops in the current chain being verified are treated\n   as a chain that has already been verified.\n\n2. the order bailout on already checked states compared current chain\n   check iterators j,k instead of using the outer loop iterator i.\n   Meaning a step backwards in states in the current chain verification\n   was being mistaken for moving to an already verified state.\n\nMove to a double mark scheme where already verified states get a\ndifferent mark, than the current chain being kept. This enables us\nto also drop the backwards verification check that was the cause of\nthe second error as any already verified state is already marked.(CVE-2026-23409)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race on rawdata dereference\n\nThere is a race condition that leads to a use-after-free situation:\nbecause the rawdata inodes are not refcounted, an attacker can start\nopen()ing one of the rawdata files, and at the same time remove the\nlast reference to this rawdata (by removing the corresponding profile,\nfor example), which frees its struct aa_loaddata; as a result, when\nseq_rawdata_open() is reached, i_private is a dangling pointer and\nfreed memory is accessed.\n\nThe rawdata inodes weren\u0026apos;t refcounted to avoid a circular refcount and\nwere supposed to be held by the profile rawdata reference.  However\nduring profile removal there is a window where the vfs and profile\ndestruction race, resulting in the use after free.\n\nFix this by moving to a double refcount scheme. Where the profile\nrefcount on rawdata is used to break the circular dependency. Allowing\nfor freeing of the rawdata once all inode references to the rawdata\nare put.(CVE-2026-23410)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix race between freeing data and fs accessing it\n\nAppArmor was putting the reference to i_private data on its end after\nremoving the original entry from the file system. However the inode\ncan aand does live beyond that point and it is possible that some of\nthe fs call back functions will be invoked after the reference has\nbeen put, which results in a race between freeing the data and\naccessing it through the fs.\n\nWhile the rawdata/loaddata is the most likely candidate to fail the\nrace, as it has the fewest references. If properly crafted it might be\npossible to trigger a race for the other types stored in i_private.\n\nFix this by moving the put of i_private referenced data to the correct\nplace which is during inode eviction.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\u0026quot;bpf: Fix too early release of tcx_entry\u0026quot;) details the\nway how the transition is happening. If tcf_block_get_ext on the q-\u0026gt;ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.(CVE-2026-23413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Purge async_hold in tls_decrypt_async_wait()\n\nThe async_hold queue pins encrypted input skbs while\nthe AEAD engine references their scatterlist data. Once\ntls_decrypt_async_wait() returns, every AEAD operation\nhas completed and the engine no longer references those\nskbs, so they can be freed unconditionally.\n\nA subsequent patch adds batch async decryption to\ntls_sw_read_sock(), introducing a new call site that\nmust drain pending AEAD operations and release held\nskbs. Move __skb_queue_purge(\u0026amp;ctx-\u0026gt;async_hold) into\ntls_decrypt_async_wait() so the purge is centralized\nand every caller -- recvmsg\u0026apos;s drain path, the -EBUSY\nfallback in tls_do_decryption(), and the new read_sock\nbatch path -- releases held skbs on synchronization\nwithout each site managing the purge independently.\n\nThis fixes a leak when tls_strp_msg_hold() fails part-way through,\nafter having added some cloned skbs to the async_hold\nqueue. tls_decrypt_sg() will then call tls_decrypt_async_wait() to\nprocess all pending decrypts, and drop back to synchronous mode, but\ntls_sw_recvmsg() only flushes the async_hold queue when one record has\nbeen processed in \u0026quot;fully-async\u0026quot; mode, which may not be the case here.\n\n[(CVE-2026-23414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxen/privcmd: restrict usage in unprivileged domU\n\nThe Xen privcmd driver allows to issue arbitrary hypercalls from\nuser space processes. This is normally no problem, as access is\nusually limited to root and the hypervisor will deny any hypercalls\naffecting other domains.\n\nIn case the guest is booted using secure boot, however, the privcmd\ndriver would be enabling a root user process to modify e.g. kernel\nmemory contents, thus breaking the secure boot feature.\n\nThe only known case where an unprivileged domU is really needing to\nuse the privcmd driver is the case when it is acting as the device\nmodel for another guest. In this case all hypercalls issued via the\nprivcmd driver will target that other guest.\n\nFortunately the privcmd driver can already be locked down to allow\nonly hypercalls targeting a specific domain, but this mode can be\nactivated from user land only today.\n\nThe target domain can be obtained from Xenstore, so when not running\nin dom0 restrict the privcmd driver to that target domain from the\nbeginning, resolving the potential problem of breaking secure boot.\n\nThis is XSA-482\n\n---\nV2:\n- defer reading from Xenstore if Xenstore isn\u0026apos;t ready yet (Jan Beulich)\n- wait in open() if target domain isn\u0026apos;t known yet\n- issue message in case no target domain found (Jan Beulich)(CVE-2026-31788)","status":"published","published":"2026-04-11T11:10:53Z","modified":"2026-08-18T01:19:47.108291933Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.087701Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-23343","title":"CVE-2026-23343 in linux - Patched by Root","description":"Root has patched CVE-2026-23343 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:46.81539972Z","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:53:31.773105Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23343","title":"CVE-2026-23343 in linux - Patched by Root","description":"Root has patched CVE-2026-23343 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:46.807146289Z","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-06T16:59:13.602872Z"},{"id":"UBUNTU-CVE-2026-23343","description":"In the Linux kernel, the following vulnerability has been resolved: xdp: produce a warning when calculated tailroom is negative Many ethernet drivers report xdp Rx queue frag size as being the same as DMA write size. However, the only user of this field, namely bpf_xdp_frags_increase_tail(), clearly expects a truesize. Such difference leads to unspecific memory corruption issues under certain circumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when running xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses all DMA-writable space in 2 buffers. This would be fine, if only rxq-\u003efrag_size was properly set to 4K, but value of 3K results in a negative tailroom, because there is a non-zero page offset. We are supposed to return -EINVAL and be done with it in such case, but due to tailroom being stored as an unsigned int, it is reported to be somewhere near UINT_MAX, resulting in a tail being grown, even if the requested offset is too much (it is around 2K in the abovementioned test). This later leads to all kinds of unspecific calltraces. [ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6 [ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4 [ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000] [ 7340.339230]  in xskxceiver[42b5,400000+69000] [ 7340.340300]  likely on CPU 6 (core 0, socket 6) [ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe [ 7340.340888]  likely on CPU 3 (core 0, socket 3) [ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7 [ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI [ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy) [ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 [ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80 [ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89 [ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202 [ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010 [ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff [ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0 [ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0 [ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500 [ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000 [ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0 [ 7340.421237] PKRU: 55555554 [ 7340.421623] Call Trace: [ 7340.421987]  \u003cTASK\u003e [ 7340.422309]  ? softleaf_from_pte+0x77/0xa0 [ 7340.422855]  swap_pte_batch+0xa7/0x290 [ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270 [ 7340.424102]  zap_pte_range+0x281/0x580 [ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240 [ 7340.425177]  unmap_page_range+0x24d/0x420 [ 7340.425714]  unmap_vmas+0xa1/0x180 [ 7340.426185]  exit_mmap+0xe1/0x3b0 [ 7340.426644]  __mmput+0x41/0x150 [ 7340.427098]  exit_mm+0xb1/0x110 [ 7340.427539]  do_exit+0x1b2/0x460 [ 7340.427992]  do_group_exit+0x2d/0xc0 [ 7340.428477]  get_signal+0x79d/0x7e0 [ 7340.428957]  arch_do_signal_or_restart+0x34/0x100 [ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0 [ 7340.430159]  do_syscall_64+0x188/ ---truncated---","status":"published","published":"2026-03-25T11:16:00Z","modified":"2026-11-06T13:52:07.730893739Z","cvss":[{"version":"4.0","score":5.6,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"medium"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-06T14:24:05.45038Z"},{"id":"AZL-80730","title":"CVE-2026-23343 affecting package kernel for versions less than 6.6.130.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T11:16:32Z","modified":"2026-08-28T17:57:01.725231Z","updated_at":"2026-11-02T15:28:10.017343Z"},{"id":"CLSA-2026-1786350974","title":"kernel: Fix of 119 CVEs","description":"- KVM: x86: Check for invalid/obsolete root *after* making MMU pages available {CVE-2026-64561}\n- KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level {CVE-2026-63807}\n- Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak {CVE-2025-40035}\n- thunderbolt: Limit XDomain response copy to actual frame size {CVE-2026-53146}\n- drm/gud: Fix UBSAN warning {CVE-2022-50628}\n- wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads {CVE-2022-49740}\n- scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests {CVE-2023-54108}\n- fs: udf: fix OOB read in lengthAllocDescs handling {CVE-2025-40044}\n- tipc: Fix use-after-free in tipc_mon_reinit_self(). {CVE-2025-40280}\n- isofs: Fix out of bound access for corrupted isofs image {CVE-2021-47478}\n- pppoe: drop PFC frames {CVE-2026-53003}\n- nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free {CVE-2026-46304}\n- net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery {CVE-2026-43466}\n- scsi: sd: fix missing put_disk() when device_add(\u0026disk_dev) fails {CVE-2026-45997}\n- irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions {CVE-2022-49716}\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check {CVE-2026-46006}\n- can: dev: can_set_termination(): allow sleeping GPIOs {CVE-2024-56625}\n- cxl/mem: Fix shutdown order {CVE-2023-52849}\n- pinctrl: check the return value of pinmux_ops::get_function_name() {CVE-2025-40030}\n- usb: usbtmc: Flush anchored URBs in usbtmc_release {CVE-2026-31758}\n- RDMA/siw: Fix potential NULL pointer dereference in header processing {CVE-2026-23242}\n- ASoC: wm_adsp: Fix NULL dereference when removing firmware controls {CVE-2026-53350}\n- net: bcmgenet: fix off-by-one in bcmgenet_put_txcb {CVE-2026-53088}\n- HID: multitouch: Check to ensure report responses match the request {CVE-2026-43047}\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23058}\n- firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle {CVE-2023-53250}\n- usb: storage: Fix memory leak in USB bulk transport {CVE-2025-68288}\n- wifi: rtw88: check for PCI upstream bridge existence {CVE-2026-46092}\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed {CVE-2026-31697}\n- scsi: qla2xxx: Fix memory leak in __qlt_24xx_handle_abts() {CVE-2022-48650}\n- HID: apple: avoid memory leak in apple_report_fixup() {CVE-2026-31520}\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() {CVE-2026-31522}\n- scsi: qla2xxx: Avoid fcport pointer dereference {CVE-2023-53603}\n- RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() {CVE-2026-46178}\n- scsi: mpi3mr: Add NULL checks when resetting request and reply queues {CVE-2026-43473}\n- HID: roccat: fix use-after-free in roccat_report_event {CVE-2026-43111}\n- tap: free page on error paths in tap_get_user_xdp() {CVE-2026-46320}\n- net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode {CVE-2026-43180}\n- usb: xhci: Fix memory leak in xhci_disable_slot() {CVE-2026-43432}\n- PCI: Fix reset_method_store() memory leak {CVE-2024-56745}\n- rbd: fix null-ptr-deref when device_add_disk() fails {CVE-2026-46079}\n- net: stmmac: fix integer underflow in chain mode {CVE-2026-31649}\n- be2net: pass wrb_params in case of OS2BMC {CVE-2025-40264}\n- thunderbolt: Validate XDomain request packet size before type cast {CVE-2026-53147}\n- Input: uinput - fix circular locking dependency with ff-core {CVE-2026-31667}\n- usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency {CVE-2023-52855}\n- nbd: defer config put in recv_work {CVE-2025-68372}\n- net: hns3: using the num_tqps in the vf driver to apply for resources {CVE-2025-71064}\n- serial: imx: fix tx statemachine deadlock {CVE-2023-52456}\n- bonding: Fix unnecessary warnings and logs from bond_xdp_get_xmit_slave() {CVE-2024-47734}\n- dm-thin: fix metadata refcount underflow {CVE-2026-46107}\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown {CVE-2026-23454}\n- usb: atm: cxacru: fix a flaw in existing endpoint checks {CVE-2025-21916}\n- md/raid5: validate payload size before accessing journal metadata {CVE-2026-46070}\n- wifi: rtw89: fix potential race condition between napi_init and napi_enable {CVE-2023-53452}\n- ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl {CVE-2021-47634}\n- ubi: ubi_create_volume: Fix use-after-free when volume creation failed {CVE-2022-49388}\n- virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false {CVE-2026-31469}\n- ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd {CVE-2025-40275}\n- ACPI: CPPC: Fix NULL pointer dereference when nosmp is used {CVE-2025-38113}\n- ACPI: video: Fix use-after-free in acpi_video_switch_brightness() {CVE-2025-40211}\n- ACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch() {CVE-2026-45982}\n- libceph: define and enforce CEPH_MAX_KEY_LEN {CVE-2026-43304}\n- ACPI: pfr_update: Fix the driver update version check {CVE-2025-39701}\n- spi: imx: fix use-after-free on unbind {CVE-2026-45996}\n- Bluetooth: bnep: reject short frames before parsing {CVE-2026-53253}\n- ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access {CVE-2026-46094}\n- xdp: produce a warning when calculated tailroom is negative {CVE-2026-23343}\n- vdpa: Add max vqp attr to vdpa_nl_policy for nlattr length check {CVE-2023-53543}\n- iomap: iomap: fix memory corruption when recording errors during writeback {CVE-2022-50406}\n- topology: Keep the cpumask unchanged when printing cpumap {CVE-2024-57917}\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers {CVE-2026-43059}\n- Bluetooth: vhci: Prevent use-after-free by removing debugfs files early {CVE-2025-39861}\n- Bluetooth: hci_sync: fix double free in 'hci_discovery_filter_clear()' {CVE-2025-38593}\n- mm/damon/sysfs: fix use-after-free in state_show() {CVE-2025-39877}\n- KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation {CVE-2026-43133}\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response {CVE-2026-43334}\n- Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() {CVE-2025-39860}\n- scsi: megaraid_sas: Fix invalid node index {CVE-2025-38239}\n- mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file {CVE-2024-42138}\n- kdb: Fix buffer overflow during tab-complete {CVE-2024-39480}\n- netfilter: nf_conntrack_h323: fix OOB read in decode_choice() {CVE-2026-43233}\n- bpf: Fix stack-out-of-bounds write in devmap {CVE-2026-23359}\n- mm/debug_vm_pgtable: clear page table entries at destroy_args() {CVE-2025-39776}\n- netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry {CVE-2026-43114}\n- gve: Account for stopped queues when reading NIC stats {CVE-2024-42162}\n- gve: Fix stats report corruption on queue count change {CVE-2026-23262}\n- amba: use generic driver_override infrastructure\n- Drivers: hv: vmbus: use generic driver_override infrastructure\n- vdpa: use generic driver_override infrastructure {CVE-2026-53118}\n- PCI: use generic driver_override infrastructure {CVE-2026-53120}\n- spi: use generic driver_override infrastructure {CVE-2026-31487}\n- driver core: platform: use generic driver_override infrastructure {CVE-2026-31527}\n- driver core: generalize driver_override in struct device {CVE-2026-31688}\n- arm64: topology: fix possible overflow in amu_fie_setup() {CVE-2022-48657}\n- nfs4_setup_readdir(): insufficient locking for -\u003ed_parent-\u003ed_inode dereferencing {CVE-2025-68185}\n- NFSD: Fix crash in nfsd4_read_release() {CVE-2025-40324}\n- rxrpc: Fix key reference count leak from call-\u003ekey {CVE-2026-31639}\n- rxrpc: Only put the call ref if one was acquired {CVE-2026-31638}\n- bpf: Set run context for rawtp test_run callback {CVE-2024-40908}\n- ethtool: Fix uninitialized number of lanes {CVE-2023-53798}\n- xsk: fix refcount underflow in error path {CVE-2023-53698}\n- net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs {CVE-2026-23340}\n- net: fix fanout UAF in packet_release() via NETDEV_UP race {CVE-2026-31504}\n- net: avoid race between device unregistration and ethnl ops {CVE-2025-21701}\n- net: sched: Disallow replacing of child qdisc from one parent to another {CVE-2025-21700}\n- libceph: Fix potential out-of-bounds access in osdmap_decode() {CVE-2026-52958}\n- libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply() {CVE-2026-46024}\n- libceph: handle rbtree insertion error in decode_choose_args() {CVE-2026-52954}\n- wifi: mac80211: ocb: skip rx_no_sta when interface is not joined {CVE-2025-71224}\n- wifi: mac80211: prohibit deactivating all links {CVE-2024-58061}\n- Bluetooth: Add check for mgmt_alloc_skb() in mgmt_remote_name() {CVE-2025-21937}\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state {CVE-2026-31773}\n- Bluetooth: Add check for mgmt_alloc_skb() in mgmt_device_connected() {CVE-2025-21936}\n- Bluetooth: fix memory leak in error path of hci_alloc_dev() {CVE-2026-53252}\n- netfilter: nf_tables: unconditionally flush pending work before notifier {CVE-2024-42109}\n- netfilter: br_netfilter: do not check confirmed bit in br_nf_local_in() after confirm {CVE-2025-39894}\n- netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case {CVE-2026-23456}\n- iavf: Fix out-of-bounds when setting channels on remove {CVE-2023-53659}\n- ipv6: prevent possible UaF in addrconf_permanent_addr() {CVE-2026-43339}\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet {CVE-2026-53112}","status":"published","published":"2026-10-21T05:41:13Z","modified":"2026-10-26T09:43:17.780926827Z","updated_at":"2026-11-02T15:43:46.850893Z"},{"id":"CLSA-2026-1789986443","title":"kernel: Fix of 121 CVEs","description":"- dlm: validate length in dlm_search_rsb_tree {CVE-2026-43125}\n- mm/damon/core: validate ranges in damon_set_regions() {CVE-2026-68165}\n- netpoll: Fix deadlock in memory allocation under spinlock {CVE-2025-68169}\n- drm/amdkfd: Check bounds on CRIU restore queue type and mqd size {CVE-2026-68258}\n- gve: fix Rx queue stall on alloc failure {CVE-2026-68129}\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved {CVE-2026-68234}\n- libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE {CVE-2026-68159}\n- media: v4l2-ctrls: validate HEVC active reference counts {CVE-2026-68206}\n- drm/i915/hdcp: check streams[] bounds before overflow {CVE-2026-68253}\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() {CVE-2026-68245}\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() {CVE-2026-68115}\n- drm/i915: Return NULL on error in active_instance {CVE-2026-68248}\n- smb: client: validate DFS referral PathConsumed {CVE-2026-68343}\n- ext4: fix use-after-free in update_super_work when racing with umount {CVE-2026-31446}\n- debugobjects: Plug race against a concurrent OOM disable {CVE-2026-68090}\n- HID: wacom: stop hardware after post-start probe failures {CVE-2026-68091}\n- drm/xe/pt: Reset current_op in xe_pt_update_ops_init() {CVE-2026-68264}\n- net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD {CVE-2026-68288}\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() {CVE-2026-68113}\n- openvswitch: fix GSO userspace truncation underflow {CVE-2026-68123}\n- drm/amd/display: use kvzalloc to allocate struct dc {CVE-2026-68436}\n- drm/i915/gem: Add missing nospec on parallel submit slot {CVE-2026-68269}\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update {CVE-2026-68394}\n- sctp: avoid auth_enable sysctl UAF during netns teardown {CVE-2026-68162}\n- wifi: mt76: mt7925: fix crash in reset link replay {CVE-2026-68307}\n- Bluetooth: hci_sync: extend conn_hash lookup critical sections {CVE-2026-68393}\n- drm/i915/gem: Fix NULL deref in I915_CONTEXT_PARAM_SSEU {CVE-2026-68243}\n- block: fix memory leak in __blkdev_issue_zero_pages {CVE-2026-68348}\n- drm/amdgpu/gfx: fix cleaner shader IB buffer overflow {CVE-2026-68276}\n- tracing: Do not call map-\u003eops-\u003eelt_free() if elt_alloc() fails {CVE-2026-64173}\n- wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin {CVE-2026-68362}\n- ovl: check access to copy_file_range source with src mounter creds {CVE-2026-68448}\n- drm/nouveau: fix reversed error cleanup order in ucopy functions {CVE-2026-68271}\n- vxlan: require CAP_NET_ADMIN in the device netns for changelink {CVE-2026-68432}\n- drm/vmwgfx: Validate vmw_surface_metadata::array_size {CVE-2026-68446}\n- net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM {CVE-2026-68296}\n- Input: elan_i2c - prevent division by zero and arithmetic underflow {CVE-2026-64275}\n- iomap: fix out-of-bounds bitmap_set() with zero-length range {CVE-2026-68145}\n- vsock: fix lock inversion in vsock_assign_transport() {CVE-2025-40231}\n- ASoC: nau8821: Cancel delayed work on component remove {CVE-2026-45963}\n- ext4: validate p_idx bounds in ext4_ext_correct_indexes {CVE-2026-31449}\n- ipc: fix memleak if msg_init_ns failed in create_ipc_ns {CVE-2024-53175}\n- tls: make sure to abort the stream if headers are bogus {CVE-2025-39946}\n- ipv6: prevent infinite loop in rt6_nlmsg_size() {CVE-2025-38588}\n- gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL {CVE-2026-23386}\n- xsk: validate MTU against usable frame size on bind {CVE-2026-43092}\n- RDMA/irdma: Harden depth calculation functions {CVE-2026-31491}\n- iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() {CVE-2026-31505}\n- net/ip6_tunnel: Prevent perpetual tunnel growth {CVE-2025-40173}\n- net/mlx5: Fix deadlock between devlink lock and esw-\u003ewq {CVE-2026-43468}\n- mm/damon/sysfs: check contexts-\u003enr before accessing contexts_arr[0] {CVE-2026-31458}\n- fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling {CVE-2026-52946}\n- nvmet: move async event work off nvmet-wq {CVE-2026-31557}\n- wifi: ath12k: Avoid memory leak while enabling statistics {CVE-2025-37743}\n- net: hns3: add vlan list lock to protect vlan list {CVE-2022-49182}\n- dmaengine: idxd: Fix leaking event log memory {CVE-2026-31440}\n- net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup {CVE-2025-68192}\n- maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() {CVE-2025-38364}\n- vfs: Don't leak disconnected dentries on umount {CVE-2025-40105}\n- mm/damon/sysfs-scheme: cleanup quotas subdirs on scheme dir setup failure {CVE-2026-23142}\n- mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure {CVE-2026-23142}\n- ceph: fix BUG_ON in __ceph_build_xattrs_blob() due to stale blob size {CVE-2026-52961}\n- ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues {CVE-2026-23166}\n- mm/migrate: fix shmem xarray update during migration {CVE-2025-22015}\n- KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish {CVE-2026-31591}\n- mm: call -\u003efree_folio() directly in folio_unmap_invalidate() {CVE-2026-31589}\n- bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu {CVE-2025-68363}\n- Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds {CVE-2026-68391}\n- net: qrtr: restrict socket creation to the initial network namespace {CVE-2026-68294}\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() {CVE-2026-68246}\n- drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers {CVE-2026-68277}\n- drm/xe: Open-code GGTT MMIO access protection {CVE-2026-23466}\n- netfilter: conntrack: add missing netlink policy validations {CVE-2026-31407}\n- futex: Prevent use-after-free during requeue-PI {CVE-2025-39977}\n- net: openvswitch: fix middle attribute validation in push_nsh() action {CVE-2025-68785}\n- iommu/vt-d: Avoid NULL pointer dereference or refcount corruption {CVE-2026-53281}\n- bpf: Free reuseport cBPF prog after RCU grace period {CVE-2026-52910}\n- net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() {CVE-2026-31700}\n- net: mana: Use pci_name() for debugfs directory naming {CVE-2026-53324}\n- netfilter: ctnetlink: ignore explicit helper on new expectations {CVE-2026-43025}\n- media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID {CVE-2025-40016}\n- net/mlx5: fw_tracer, Validate format string parameters {CVE-2025-68816}\n- ext4: avoid infinite loops caused by residual data {CVE-2026-31448}\n- Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ {CVE-2026-43134}\n- ext4: publish jinode after initialization {CVE-2026-31450}\n- drm/amdkfd: validate SVM ioctl nattr against buffer size {CVE-2026-46197}\n- drm/i915/gem: Fix phys BO pread/pwrite with offset {CVE-2026-53356}\n- net/mlx5: HWS, change error flow on matcher disconnect {CVE-2025-21751}\n- RDMA/irdma: Prevent rereg_mr for non-mem regions {CVE-2026-68419}\n- net/mlx5e: xsk: Fix unlocked writing to ICOSQ {CVE-2026-64210}\n- hwmon: (lm90) Add lock protection to lm90_alert {CVE-2026-64213}\n- RDMA/srp: bound SRP_RSP sense copy by the received length {CVE-2026-53186}\n- RDMA/siw: Remove direct link to net_device {CVE-2024-57857}\n- tracing: Fix reading strings from synthetic events {CVE-2022-50255}\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() {CVE-2026-43437}\n- HID: core: Mitigate potential OOB by removing bogus memset() {CVE-2026-43048}\n- xfrm: Wait for RCU readers during policy netns exit {CVE-2026-43091}\n- wifi: mac80211: fix FILS discovery and unsol BPR double free {CVE-2026-64568}\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation {CVE-2026-68257}\n- maple_tree: set MA_STATE_PREALLOC on zero-allocation early exits {CVE-2025-38364}\n- netfilter: nf_tables: make nft_object rhltable per table {CVE-2026-74565}\n- iommu/amd: serialize sequence allocation under concurrent TLB invalidations {CVE-2026-43253}\n- Bluetooth: hci_sync: fix double free in 'hci_discovery_filter_clear()' {CVE-2025-38593}\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete {CVE-2026-43059}\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers {CVE-2026-43059}\n- Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete {CVE-2026-43059}\n- ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF {CVE-2026-68398}\n- libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update {CVE-2026-68156}\n- Bluetooth: bnep: reject short frames before parsing {CVE-2026-53253}\n- geneve: require CAP_NET_ADMIN in the device netns for changelink {CVE-2026-68142}\n- net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink {CVE-2026-68142}\n- ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() {CVE-2026-68160}\n- libceph: Reject monmaps advertising zero monitors {CVE-2026-68155}\n- sctp: fix auth_hmacs array size in struct sctp_cookie {CVE-2026-68376}\n- ALSA: seq: close a re-opened queue timer in the destructor {CVE-2026-68202}\n- KVM: SVM: Bump asid_generation on CPU online to avoid ASID collision after hotplug {CVE-2026-68093}\n- net/sched: act_tunnel_key: Defer dst_release to RCU callback {CVE-2026-68377}\n- drm/amdgpu/vce: fix integer overflow in image size {CVE-2026-68108}\n- nfs: use nfsi-\u003erwsem to protect traversal of the file lock list {CVE-2026-72472}\n- Bluetooth: RFCOMM: Fix session UAF in set_termios {CVE-2026-68188}\n- RDMA/umem: Fix truncation for block sizes \u003e= 4G {CVE-2026-53133}\n- xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() {CVE-2026-53250}\n- spi: imx: fix use-after-free on unbind {CVE-2026-45996}\n- xdp: produce a warning when calculated tailroom is negative {CVE-2026-23343}\n- cxl/mbox: validate payload size before accessing contents in cxl_payload_from_user_allowed() {CVE-2026-23327}\n- gve: Fix stats report corruption on queue count change {CVE-2026-23262}","status":"published","published":"2026-09-21T10:29:04Z","modified":"2026-10-26T09:43:19.659596137Z","updated_at":"2026-11-02T15:43:48.28229Z"},{"id":"CVE-2026-23343","title":"xdp: produce a warning when calculated tailroom is negative","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxdp: produce a warning when calculated tailroom is negative\n\nMany ethernet drivers report xdp Rx queue frag size as being the same as\nDMA write size. However, the only user of this field, namely\nbpf_xdp_frags_increase_tail(), clearly expects a truesize.\n\nSuch difference leads to unspecific memory corruption issues under certain\ncircumstances, e.g. in ixgbevf maximum DMA write size is 3 KB, so when\nrunning xskxceiver's XDP_ADJUST_TAIL_GROW_MULTI_BUFF, 6K packet fully uses\nall DMA-writable space in 2 buffers. This would be fine, if only\nrxq-\u003efrag_size was properly set to 4K, but value of 3K results in a\nnegative tailroom, because there is a non-zero page offset.\n\nWe are supposed to return -EINVAL and be done with it in such case, but due\nto tailroom being stored as an unsigned int, it is reported to be somewhere\nnear UINT_MAX, resulting in a tail being grown, even if the requested\noffset is too much (it is around 2K in the abovementioned test). This later\nleads to all kinds of unspecific calltraces.\n\n[ 7340.337579] xskxceiver[1440]: segfault at 1da718 ip 00007f4161aeac9d sp 00007f41615a6a00 error 6\n[ 7340.338040] xskxceiver[1441]: segfault at 7f410000000b ip 00000000004042b5 sp 00007f415bffecf0 error 4\n[ 7340.338179]  in libc.so.6[61c9d,7f4161aaf000+160000]\n[ 7340.339230]  in xskxceiver[42b5,400000+69000]\n[ 7340.340300]  likely on CPU 6 (core 0, socket 6)\n[ 7340.340302] Code: ff ff 01 e9 f4 fe ff ff 0f 1f 44 00 00 4c 39 f0 74 73 31 c0 ba 01 00 00 00 f0 0f b1 17 0f 85 ba 00 00 00 49 8b 87 88 00 00 00 \u003c4c\u003e 89 70 08 eb cc 0f 1f 44 00 00 48 8d bd f0 fe ff ff 89 85 ec fe\n[ 7340.340888]  likely on CPU 3 (core 0, socket 3)\n[ 7340.345088] Code: 00 00 00 ba 00 00 00 00 be 00 00 00 00 89 c7 e8 31 ca ff ff 89 45 ec 8b 45 ec 85 c0 78 07 b8 00 00 00 00 eb 46 e8 0b c8 ff ff \u003c8b\u003e 00 83 f8 69 74 24 e8 ff c7 ff ff 8b 00 83 f8 0b 74 18 e8 f3 c7\n[ 7340.404334] Oops: general protection fault, probably for non-canonical address 0x6d255010bdffc: 0000 [#1] SMP NOPTI\n[ 7340.405972] CPU: 7 UID: 0 PID: 1439 Comm: xskxceiver Not tainted 6.19.0-rc1+ #21 PREEMPT(lazy)\n[ 7340.408006] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[ 7340.409716] RIP: 0010:lookup_swap_cgroup_id+0x44/0x80\n[ 7340.410455] Code: 83 f8 1c 73 39 48 ba ff ff ff ff ff ff ff 03 48 8b 04 c5 20 55 fa bd 48 21 d1 48 89 ca 83 e1 01 48 d1 ea c1 e1 04 48 8d 04 90 \u003c8b\u003e 00 48 83 c4 10 d3 e8 c3 cc cc cc cc 31 c0 e9 98 b7 dd 00 48 89\n[ 7340.412787] RSP: 0018:ffffcc5c04f7f6d0 EFLAGS: 00010202\n[ 7340.413494] RAX: 0006d255010bdffc RBX: ffff891f477895a8 RCX: 0000000000000010\n[ 7340.414431] RDX: 0001c17e3fffffff RSI: 00fa070000000000 RDI: 000382fc7fffffff\n[ 7340.415354] RBP: 00fa070000000000 R08: ffffcc5c04f7f8f8 R09: ffffcc5c04f7f7d0\n[ 7340.416283] R10: ffff891f4c1a7000 R11: ffffcc5c04f7f9c8 R12: ffffcc5c04f7f7d0\n[ 7340.417218] R13: 03ffffffffffffff R14: 00fa06fffffffe00 R15: ffff891f47789500\n[ 7340.418229] FS:  0000000000000000(0000) GS:ffff891ffdfaa000(0000) knlGS:0000000000000000\n[ 7340.419489] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 7340.420286] CR2: 00007f415bfffd58 CR3: 0000000103f03002 CR4: 0000000000772ef0\n[ 7340.421237] PKRU: 55555554\n[ 7340.421623] Call Trace:\n[ 7340.421987]  \u003cTASK\u003e\n[ 7340.422309]  ? softleaf_from_pte+0x77/0xa0\n[ 7340.422855]  swap_pte_batch+0xa7/0x290\n[ 7340.423363]  zap_nonpresent_ptes.constprop.0.isra.0+0xd1/0x270\n[ 7340.424102]  zap_pte_range+0x281/0x580\n[ 7340.424607]  zap_pmd_range.isra.0+0xc9/0x240\n[ 7340.425177]  unmap_page_range+0x24d/0x420\n[ 7340.425714]  unmap_vmas+0xa1/0x180\n[ 7340.426185]  exit_mmap+0xe1/0x3b0\n[ 7340.426644]  __mmput+0x41/0x150\n[ 7340.427098]  exit_mm+0xb1/0x110\n[ 7340.427539]  do_exit+0x1b2/0x460\n[ 7340.427992]  do_group_exit+0x2d/0xc0\n[ 7340.428477]  get_signal+0x79d/0x7e0\n[ 7340.428957]  arch_do_signal_or_restart+0x34/0x100\n[ 7340.429571]  exit_to_user_mode_loop+0x8e/0x4c0\n[ 7340.430159]  do_syscall_64+0x188/\n---truncated---","status":"published","published":"2026-03-25T10:27:31.13Z","modified":"2026-11-07T02:30:28.395339834Z","updated_at":"2026-11-07T03:07:40.684996Z"},{"id":"MGASA-2026-0097","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:41.57748Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0098","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:42.526844Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2026:20572-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T17:16:35Z","modified":"2026-04-22T08:16:13.517421Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"SUSE-SU-2026:21114-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T17:04:49Z","modified":"2026-04-18T18:25:53.212585Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21123-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T18:28:29Z","modified":"2026-04-18T18:25:56.735736Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21230-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:11:07Z","modified":"2026-07-09T18:29:49.212435035Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21237-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:44:52Z","modified":"2026-04-23T18:26:50.344244Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21255-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Micro (RT) 6.0 and 6.1 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: register hooks last when adding new chain/flowtable (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: export bpf_link_inc_not_zero (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- comedi: Reinit dev-spinlock between attachments to low-level drivers (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: don't use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186 bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669 ltc#212590).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669 ltc#212590).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: don't power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Don't default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-17T15:00:24Z","modified":"2026-04-24T18:25:08.602484Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21352-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:09:00Z","modified":"2026-04-29T18:23:57.904042Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21361-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:44:52Z","modified":"2026-04-29T18:23:57.770283Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:2217-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-2023-20585: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2025-68310: s390/pci: Use pci_uevent_ers() in PCI recovery (bsc#1255160).\n- CVE-2025-71183: btrfs: always detect conflicting inodes when logging inode refs (bsc#1257631).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: move dev_xmit_recursion() helpers to net/core/dev.h (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23346: mm/ioremap: define generic_ioremap_prot() and generic_iounmap() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23461: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (bsc#1261707).\n- CVE-2026-23462: Bluetooth: HIDP: Fix possible UAF (bsc#1261710).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31404: xfs: avoid dereferencing log items after push callbacks (bsc#1261628).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31436: dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (bsc#1262602).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31470: virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (bsc#1262665).\n- CVE-2026-31488: drm/amd/display: Do not skip unrelated mode changes in DSC validation (bsc#1262746).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31512: Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n  (bsc#1262734).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31570: can: gw: fix OOB heap access in cgw_csum_crc8_rel() (bsc#1263065).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31602: ALSA: ctxfi: Limit PTP to a single page (bsc#1263723).\n- CVE-2026-31607: usbip: validate number_of_packets in usbip_pack_ret_submit() (bsc#1263600).\n- CVE-2026-31622: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (bsc#1263797).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31656: drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (bsc#1263170).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43044: crypto: caam - fix DMA corruption on long hmac keys (bsc#1264087).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43110: wifi: brcmfmac: validate bsscfg indices in IF events (bsc#1264482).\n- CVE-2026-43120: RDMA/irdma: Fix double free related to rereg_user_mr.\n- CVE-2026-43126: ALSA: mixer: oss: Add card disconnect checkpoints (bsc#1264634).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43214: KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (bsc#1264651).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43330: crypto: caam - fix overflow on long hmac keys (bsc#1264801).\n- CVE-2026-43334: Bluetooth: SMP: force responder MITM requirements before building the pairing response (bsc#1265090).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43419: ceph: fix memory leaks in ceph_mdsc_build_path() (bsc#1264661).\n- CVE-2026-43437: ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (bsc#1265126).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for 'VAD Detected' (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- btrfs: do not skip logging new dentries when logging a new name (git-fixes).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- cgroup/cpuset: Fix incorrect change to effective_xcpus in partition_xcpus_del() (bsc#1241166).\n- cgroup/cpuset: Fix incorrect use of cpuset_update_tasks_cpumask() in update_cpumasks_hier() (bsc#1241166).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- checkpatch: add support for Assisted-by tag (stable-fixes).\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from 'scaling factor' list (bsc#1249104).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: arm64/aes - Fix 32-bit aes_mac_update() arg treated as 64-bit (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: authencesn - reject short ahash digests during instance creation (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: testmgr - Hide ENOENT errors (stable-fixes).\n- crypto: testmgr - Hide ENOENT errors better (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: Fix output pin registration (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix the idr allocation flags (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/msm: add missing MODULE_DEVICE_ID definitions (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: add vm_ops to dlfb_ops_mmap to prevent use-after-free (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: playstation: Clamp num_touch_reports (git-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- ice: set max queues in alloc_etherdev_mqs() (git-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request 'event' (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- intel_idle: add Clearwater Forest SoC support (jsc#PED-10383).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- irqchip/irq-pic32-evic: Address warning related to wrong printf() formatter (git-fixes).\n- kdump, documentation: describe craskernel CMA reservation (jsc#PED-7249).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing (bsc#1253122).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: Convert to platform remove callback returning void (stable-fixes).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Factor out common write operation to `sst_nor_write_data()` (stable-fixes).\n- mtd: spi-nor: sst: Fix SST write failure (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of 'old' filters before change() (git-fixes).\n- net/sched: fix pedit partial COW leading to page cache corruption (bsc#1265421).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-fabrics: use kfree_sensitive() for DHCHAP secrets (git-fixes).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: cap queue creation to used queues (git-fixes).\n- nvme-pci: ensure we're polling a polled queue (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- Partial revert 'x86/xen: fix balloon target initialization for PVH dom0' (bsc#1262599).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (git-fixes).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse 'nvidia,refclk-select' (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86/intel: power-domains: Add Clearwater Forest support (jsc#PED-16221).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: ISST: Add Clearwater Forest to support list (jsc#PED-16221).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert 'ALSA: usb: Increase volume range that triggers a warning' (git-fixes).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259995).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259995).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259995).\n- sched/balancing: Switch the 'DEFINE_SPINLOCK(balancing)' spinlock into an 'atomic_t sched_balance_running' flag\n  (bsc#1253754).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1253754).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1253754).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669 ltc#212590).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669 ltc#212590).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: Use helper function devm_clk_get_enabled() (stable-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: spi-ti-qspi: Convert to platform remove callback returning void (stable-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun4i: switch to use modern name (stable-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: synquacer: switch to use modern name (stable-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: uniphier: switch to use modern name (stable-fixes).\n- spi: zynq-qspi: switch to use modern name (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: added bound check to geoid (stable-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tty: tty_io: update timestamps on all device nodes (bsc#1262020).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (stable-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (stable-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (stable-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: ath11k: skip status ring entry processing (stable-fixes).\n- wifi: ath11k: Use dma_alloc_noncoherent for rx_tid buffer allocation (stable-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert 'Fix locking in error paths' (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- workqueue: Break up enum definitions and give names to the types (bsc#1260522).\n- workqueue: Clean up enum work_bits and related constants (bsc#1260522).\n- workqueue: Factor out work_grab_pending() from __cancel_work_sync() (bsc#1260522).\n- workqueue: Fix UBSAN 'subtraction overflow' error in shift_and_mask() (bsc#1260522).\n- workqueue: Implement disable/enable for (delayed) work items (bsc#1260522).\n- workqueue: Introduce work_cancel_flags (bsc#1260522).\n- workqueue: Make @flags handling consistent across set_work_data() and friends (bsc#1260522).\n- workqueue: Preserve OFFQ bits in cancel[_sync] paths (bsc#1260522).\n- workqueue: Rename __cancel_work_timer() to __cancel_timer_sync() (bsc#1260522).\n- workqueue: Reorganize flush and cancel[_sync] functions (bsc#1260522).\n- x86/boot/64: Clear most of CR4 in startup_64(), except PAE, MCE and LA57 (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot: Don't add the EFI stub to targets, again (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add models 0x60-0x6f to the Zen5 range (bsc#1263255).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask (git-fixes).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Remove ENDBR64 from FRED entry points (git-fixes).\n- x86: KVM: Advertise CPUIDs for new instructions in Clearwater Forest (jsc#PED-16245).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n- xfrm: esp: avoid in-place decrypt on shared skb frags (bsc#1264449).\n","status":"published","published":"2026-06-02T05:58:33Z","modified":"2026-06-03T08:30:23.364112563Z","updated_at":"2026-11-02T15:54:02.654057Z"},{"id":"SUSE-SU-2026:2238-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-2023-20585: x86/CPU: Fix FPDSS on Zen1 (bsc#1243603).\n- CVE-2025-54518: x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache (bsc#1264013).\n- CVE-2025-68310: s390/pci: Use pci_uevent_ers() in PCI recovery (bsc#1255160).\n- CVE-2025-71183: btrfs: always detect conflicting inodes when logging inode refs (bsc#1257631).\n- CVE-2026-23168: flex_proportions: make fprop_new_period() hardirq safe (bsc#1258826).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23245: net/sched: act_gate: snapshot parameters with RCU on replace (bsc#1259799).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23271: perf: Fix __perf_event_overflow() vs perf_remove_from_context() race (bsc#1260018).\n- CVE-2026-23276: net: move dev_xmit_recursion() helpers to net/core/dev.h (bsc#1260012).\n- CVE-2026-23300: net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop (bsc#1260538).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23313: i40e: Fix preempt count leak in napi poll tracepoint (bsc#1260555).\n- CVE-2026-23321: mptcp: pm: in-kernel: always mark signal+subflow endp as used (bsc#1260505).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23340: net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs (bsc#1260523).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23346: mm/ioremap: define generic_ioremap_prot() and generic_iounmap() (bsc#1260529).\n- CVE-2026-23351: netfilter: nft_set_pipapo: split gc into unlink and reclaim phase (bsc#1260526).\n- CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint() (bsc#1260801).\n- CVE-2026-23368: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock (bsc#1260530).\n- CVE-2026-23374: blktrace: fix __this_cpu_read/write in preemptible context (bsc#1260811).\n- CVE-2026-23378: net/sched: act_ife: Fix metalist update behavior (bsc#1260546).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23391: netfilter: xt_CT: drop pending enqueued packets on template removal (bsc#1260566).\n- CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error (bsc#1260531).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23397: nfnetlink_osf: validate individual option lengths in fingerprints (bsc#1260728).\n- CVE-2026-23399: nf_tables: nft_dynset: fix possible stateful expression memleak in error path (bsc#1261020).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23440: net/mlx5e: Fix race condition during IPSec ESN update (bsc#1261641).\n- CVE-2026-23441: net/mlx5e: Prevent concurrent access to IPSec ASO context (bsc#1261768).\n- CVE-2026-23442: ipv6: add NULL checks for idev in SRv6 paths (bsc#1261581).\n- CVE-2026-23445: igc: fix page fault in XDP TX timestamps handling (bsc#1261702).\n- CVE-2026-23449: net/sched: teql: Fix double-free in teql_master_xmit (bsc#1261779).\n- CVE-2026-23450: net/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock() (bsc#1261584).\n- CVE-2026-23455: netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() (bsc#1261687).\n- CVE-2026-23456: netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case (bsc#1261703).\n- CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp() (bsc#1261686).\n- CVE-2026-23458: netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct() (bsc#1261781).\n- CVE-2026-23461: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (bsc#1261707).\n- CVE-2026-23462: Bluetooth: HIDP: Fix possible UAF (bsc#1261710).\n- CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion (bsc#1261692).\n- CVE-2026-23472: serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN (bsc#1261636).\n- CVE-2026-23473: io_uring/poll: fix multishot recv missing EOF on wakeup race (bsc#1261694).\n- CVE-2026-31395: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler (bsc#1261786).\n- CVE-2026-31400: sunrpc: fix cache_request leak in cache_release (bsc#1261645).\n- CVE-2026-31402: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache (bsc#1261638).\n- CVE-2026-31403: NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd (bsc#1261796).\n- CVE-2026-31404: xfs: avoid dereferencing log items after push callbacks (bsc#1261628).\n- CVE-2026-31407: netfilter: conntrack: add missing netlink policy validations (bsc#1261632).\n- CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send() (bsc#1261752).\n- CVE-2026-31415: ipv6: avoid overflows in ip6_datagram_send_ctl() (bsc#1262099).\n- CVE-2026-31416: netfilter: nfnetlink_log: account for netlink header size (bsc#1262100).\n- CVE-2026-31420: bridge: mrp: reject zero test interval to avoid OOM panic (bsc#1262055).\n- CVE-2026-31421: net/sched: cls_fw: fix NULL pointer dereference on shared blocks (bsc#1262061).\n- CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks (bsc#1262054).\n- CVE-2026-31423: net/sched: sch_hfsc: fix divide-by-zero in rtsc_min() (bsc#1262063).\n- CVE-2026-31424: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP (bsc#1262053).\n- CVE-2026-31425: rds: ib: reject FRMR registration before IB connection is established (bsc#1262074).\n- CVE-2026-31427: netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (bsc#1262086).\n- CVE-2026-31428: netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (bsc#1262087).\n- CVE-2026-31436: dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (bsc#1262602).\n- CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes (bsc#1262616).\n- CVE-2026-31470: virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (bsc#1262665).\n- CVE-2026-31488: drm/amd/display: Do not skip unrelated mode changes in DSC validation (bsc#1262746).\n- CVE-2026-31494: net: cadence: macb: Synchronize stats calculations (bsc#1262671).\n- CVE-2026-31496: netfilter: nf_conntrack_expect: skip expectations in other netns via proc (bsc#1262673).\n- CVE-2026-31504: net: fix fanout UAF in packet_release() via NETDEV_UP race (bsc#1263085).\n- CVE-2026-31505: iavf: fix out-of-bounds writes in iavf_get_ethtool_stats() (bsc#1263093).\n- CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer (bsc#1263095).\n- CVE-2026-31512: Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n  (bsc#1262734).\n- CVE-2026-31515: af_key: validate families in pfkey_send_migrate() (bsc#1262752).\n- CVE-2026-31519: btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (bsc#1263012).\n- CVE-2026-31525: bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN (bsc#1262725).\n- CVE-2026-31528: perf: Make sure to use pmu_ctx-\u003epmu for groups (bsc#1263001).\n- CVE-2026-31533: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption (bsc#1262758).\n- CVE-2026-31547: drm/xe: Fix missing runtime PM reference in ccs_mode_store (bsc#1263018).\n- CVE-2026-31550: pmdomain: bcm: bcm2835-power: Increase ASB control timeout (bsc#1263104).\n- CVE-2026-31565: RDMA/irdma: Fix deadlock during netdev reset with active connections (bsc#1263064).\n- CVE-2026-31570: can: gw: fix OOB heap access in cgw_csum_crc8_rel() (bsc#1263065).\n- CVE-2026-31586: mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() (bsc#1263176).\n- CVE-2026-31588: KVM: x86: Use scratch field in MMIO fragment to hold small write values (bsc#1263165).\n- CVE-2026-31602: ALSA: ctxfi: Limit PTP to a single page (bsc#1263723).\n- CVE-2026-31607: usbip: validate number_of_packets in usbip_pack_ret_submit() (bsc#1263600).\n- CVE-2026-31622: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (bsc#1263797).\n- CVE-2026-31649: net: stmmac: fix integer underflow in chain mode (bsc#1263582).\n- CVE-2026-31656: drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (bsc#1263170).\n- CVE-2026-31662: tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG (bsc#1263131).\n- CVE-2026-31668: seg6: separate dst_cache for input and output paths in seg6 lwtunnel (bsc#1263140).\n- CVE-2026-31669: mptcp: fix slab-use-after-free in __inet_lookup_established (bsc#1263141).\n- CVE-2026-31675: net/sched: sch_netem: fix out-of-bounds access in packet corruption (bsc#1263556).\n- CVE-2026-31679: openvswitch: validate MPLS set/set_masked payload length (bsc#1263592).\n- CVE-2026-31681: netfilter: xt_multiport: validate range encoding in checkentry (bsc#1263593).\n- CVE-2026-31682: bridge: br_nd_send: linearize skb before parsing ND options (bsc#1263595).\n- CVE-2026-31684: net: sched: act_csum: validate nested VLAN headers (bsc#1263596).\n- CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets (bsc#1263668).\n- CVE-2026-31694: fuse: reject oversized dirents in page cache (bsc#1263901).\n- CVE-2026-31700: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() (bsc#1263882).\n- CVE-2026-31738: vxlan: validate ND option lengths in vxlan_na_create (bsc#1264059).\n- CVE-2026-31787: xen/privcmd: fix double free via VMA splitting (bsc#1262181).\n- CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking (bsc#1264014).\n- CVE-2026-43025: netfilter: ctnetlink: ignore explicit helper on new expectations (bsc#1263931).\n- CVE-2026-43027: netfilter: nf_conntrack_helper: pass helper to expect cleanup (bsc#1263933).\n- CVE-2026-43037: ip6_tunnel: clear skb2-\u003ecb in ip4ip6_err() (bsc#1263995).\n- CVE-2026-43038: ipv6: icmp: clear skb2-\u003ecb in ip6_err_gen_icmpv6_unreach() (bsc#1264097).\n- CVE-2026-43044: crypto: caam - fix DMA corruption on long hmac keys (bsc#1264087).\n- CVE-2026-43050: atm: lec: fix use-after-free in sock_def_readable() (bsc#1264082).\n- CVE-2026-43060: netfilter: nft_ct: drop pending enqueued packets on removal (bsc#1264183).\n- CVE-2026-43088: net: af_key: zero aligned sockaddr tail in PF_KEY exports (bsc#1264469).\n- CVE-2026-43110: wifi: brcmfmac: validate bsscfg indices in IF events (bsc#1264482).\n- CVE-2026-43120: RDMA/irdma: Fix double free related to rereg_user_mr.\n- CVE-2026-43126: ALSA: mixer: oss: Add card disconnect checkpoints (bsc#1264634).\n- CVE-2026-43190: netfilter: xt_tcpmss: check remaining length before reading optlen (bsc#1264848).\n- CVE-2026-43214: KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2() (bsc#1264651).\n- CVE-2026-43265: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() (bsc#1264427).\n- CVE-2026-43329: netfilter: flowtable: strictly check for maximum number of actions (bsc#1265085).\n- CVE-2026-43330: crypto: caam - fix overflow on long hmac keys (bsc#1264801).\n- CVE-2026-43334: Bluetooth: SMP: force responder MITM requirements before building the pairing response (bsc#1265090).\n- CVE-2026-43365: xfs: fix undersized l_iclog_roundoff values (bsc#1265119).\n- CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle (bsc#1265116).\n- CVE-2026-43419: ceph: fix memory leaks in ceph_mdsc_build_path() (bsc#1264661).\n- CVE-2026-43437: ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (bsc#1265126).\n- CVE-2026-43441: net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1264674).\n- CVE-2026-43494: net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- CVE-2026-43503: net: skbuff: propagate shared-frag marker through frag-transfer helpers (bsc#1265960).\n- CVE-2026-46300: net: skbuff: preserve shared-frag marker during coalescing (bsc#1265209).\n- CVE-2026-46331: kernel: net/sched: fix pedit partial COW leading to page cache (bsc#1265421)\n\nThe following non security issues were fixed:\n\n- accel/qaic: Add overflow check to remap_pfn_range during mmap (git-fixes).\n- ACPI: AGDI: fix missing newline in error message (git-fixes).\n- ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug (git-fixes).\n- ACPI: scan: Use acpi_dev_put() in object add error paths (git-fixes).\n- ACPI: video: Add backlight=native quirk for Dell OptiPlex 7770 AIO (git-fixes).\n- ACPI: video: force native backlight on HP OMEN 16 (8A44) (stable-fixes).\n- ALSA: 6fire: Fix input volume change detection (git-fixes).\n- ALSA: 6fire: fix use-after-free on disconnect (git-fixes).\n- ALSA: aoa: i2sbus: clear stale prepared state (git-fixes).\n- ALSA: aoa: i2sbus: fix OF node lifetime handling (git-fixes).\n- ALSA: aoa: Skip devices with no codecs in i2sbus_resume() (git-fixes).\n- ALSA: aoa: Use guard() for mutex locks (stable-fixes).\n- ALSA: asihpi: avoid write overflow check warning (stable-fixes).\n- ALSA: caiaq: Don't abort when no input device is available (git-fixes).\n- ALSA: caiaq: Fix control_put() result and cache rollback (git-fixes).\n- ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path (git-fixes).\n- ALSA: caiaq: fix usb_dev refcount leak on probe failure (git-fixes).\n- ALSA: caiaq: Handle probe errors properly (git-fixes).\n- ALSA: caiaq: take a reference on the USB device in create_card() (git-fixes).\n- ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() (git-fixes).\n- ALSA: core: Fix potential data race at fasync handling (git-fixes).\n- ALSA: core: Serialize deferred fasync state checks (git-fixes).\n- ALSA: core: Validate compress device numbers without dynamic minors (git-fixes).\n- ALSA: ctxfi: Add fallback to default RSR for S/PDIF (git-fixes).\n- ALSA: ctxfi: Fix missing SPDIFI1 index handling (stable-fixes).\n- ALSA: ctxfi: Limit PTP to a single page (git-fixes).\n- ALSA: firewire-tascam: Do not drop unread control events (git-fixes).\n- ALSA: fireworks: bound device-supplied status before string array lookup (git-fixes).\n- ALSA: hda/realtek - fixed speaker no sound update (git-fixes).\n- ALSA: hda/realtek: Add HP ENVY Laptop 13-ba0xxx quirk (stable-fixes).\n- ALSA: hda/realtek: Add mute LED quirk for HP Pavilion 15-eg0xxx (stable-fixes).\n- ALSA: hda/realtek: Add quirk for ASUS ROG Flow Z13-KJP GZ302EAC (stable-fixes).\n- ALSA: hda/realtek: add quirk for Framework F111:000F (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 14IAH10 (stable-fixes).\n- ALSA: hda/realtek: fix code style (ERROR: else should follow close brace '}') (git-fixes).\n- ALSA: hda: cs35l41: Put ACPI device on missing physical node (git-fixes).\n- ALSA: hda: cs35l56: Propagate ASP TX source control errors (git-fixes).\n- ALSA: hda: cs35l56: Put ACPI device after setting companion (git-fixes).\n- ALSA: hda: Fix NULL pointer dereference in snd_hda_ctl_add() (git-fixes).\n- ALSA: misc: Use guard() for spin locks (stable-fixes).\n- ALSA: scarlett2: Add missing error check when initialise Autogain Status (git-fixes).\n- ALSA: scarlett2: Add missing sentinel initializer field (git-fixes).\n- ALSA: seq: Notify client and port info changes (stable-fixes).\n- ALSA: seq_oss: return full count for successful SEQ_FULLSIZE writes (stable-fixes).\n- ALSA: usb-audio: apply quirk for MOONDROP JU Jiu (stable-fixes).\n- ALSA: usb-audio: Avoid false E-MU sample-rate notifications (git-fixes).\n- ALSA: usb-audio: Avoid potential endless loop in convert_chmap_v3() (git-fixes).\n- ALSA: usb-audio: Bound MIDI 2.0 endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Bound MIDI endpoint descriptor scans (git-fixes).\n- ALSA: usb-audio: Evaluate packsize caps at the right place (git-fixes).\n- ALSA: usb-audio: Fix Audio Advantage Micro II SPDIF switch (git-fixes).\n- ALSA: usb-audio: Fix potential leak of pd at parsing UAC3 streams (git-fixes).\n- ALSA: usb-audio: Fix quirk flags for NeuralDSP Quad Cortex (stable-fixes).\n- ALSA: usb-audio: Fix UAC3 cluster descriptor size check (git-fixes).\n- ALSA: usb-audio: midi2: Restart output URBs on resume (git-fixes).\n- ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES (git-fixes).\n- amdgpu/jpeg: fix deepsleep register for jpeg 5_0_0 and 5_0_2 (stable-fixes).\n- ASoC: amd: acp: Add DMI quirk for Valve Steam Deck OLED (git-fixes).\n- ASoC: amd: yc: Add DMI entry for HP Laptop 15-fc0xxx (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK BM1403CDA (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Thin A15 B7VF (stable-fixes).\n- ASoC: amd: yc: Add HP OMEN Gaming Laptop 16-ap0xxx product line in quirk table (stable-fixes).\n- ASoC: codecs: ab8500: Fix casting of private data (git-fixes).\n- ASoC: cs35l56: Destroy workqueue in probe error path (git-fixes).\n- ASoC: cs35l56: Don't use devres to unregister component (git-fixes).\n- ASoC: cs35l56: Fix hibernate write in runtime resume error path (git-fixes).\n- ASoC: fsl_easrc: Change the type for iec958 channel status controls (git-fixes).\n- ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() (git-fixes).\n- ASoC: fsl_easrc: fix comment typo (git-fixes).\n- ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() (git-fixes).\n- ASoC: fsl_micfil: Add access property for 'VAD Detected' (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() (git-fixes).\n- ASoC: fsl_micfil: Fix event generation in micfil_quality_set() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation for cached controls (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() (git-fixes).\n- ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() (git-fixes).\n- ASoC: Intel: bytcr_wm5102: Fix MCLK leak on platform_clock_control error (git-fixes).\n- ASoC: qcom: q6apm-dai: reset queue ptr on trigger stop (git-fixes).\n- ASoC: qcom: q6apm-lpass-dai: Fix multiple graph opens (git-fixes).\n- ASoC: qcom: q6apm: move component registration to unmanaged version (git-fixes).\n- ASoC: qcom: q6apm: remove child devices when apm is removed (git-fixes).\n- ASoC: qcom: qdsp6: topology: check widget type before accessing data (git-fixes).\n- ASoC: soc-core: call missing INIT_LIST_HEAD() for card_aux_list (stable-fixes).\n- ASoC: SOF: compress: return the configured codec from get_params (git-fixes).\n- ASoC: SOF: Don't allow pointer operations on unconfigured streams (git-fixes).\n- ASoC: SOF: Intel: hda: Place check before dereference (git-fixes).\n- ASoC: SOF: topology: reject invalid vendor array size in token parser (stable-fixes).\n- ASoC: sti: Return errors from regmap_field_alloc() (git-fixes).\n- ASoC: sti: use managed regmap_field allocations (git-fixes).\n- ASoC: stm32_sai: fix incorrect BCLK polarity for DSP_A/B, LEFT_J (stable-fixes).\n- ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585 (stable-fixes).\n- batman-adv: bla: only purge non-released claims (git-fixes).\n- batman-adv: bla: prevent use-after-free when deleting claims (git-fixes).\n- batman-adv: bla: put backbone reference on failed claim hash insert (git-fixes).\n- batman-adv: fix integer overflow on buff_pos (git-fixes).\n- batman-adv: hold claim backbone gateways by reference (git-fixes).\n- batman-adv: reject new tp_meter sessions during teardown (git-fixes).\n- batman-adv: reject oversized global TT response buffers (git-fixes).\n- batman-adv: stop caching unowned originator pointers in BAT IV (git-fixes).\n- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling (git-fixes).\n- Bluetooth: btmtk: validate WMT event SKB length before struct access (git-fixes).\n- Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER (git-fixes).\n- Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in SSP passkey handlers (git-fixes).\n- Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (git-fixes).\n- Bluetooth: HIDP: serialise l2cap_unregister_user via hidp_session_sem (git-fixes).\n- Bluetooth: ISO: Fix data-race on dst in iso_sock_connect() (git-fixes).\n- Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp (git-fixes).\n- Bluetooth: l2cap: fix MPS check in l2cap_ecred_reconf_req (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_connection_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb() (git-fixes).\n- Bluetooth: L2CAP: Fix printing wrong information if SDU length exceeds MTU (git-fixes).\n- Bluetooth: RFCOMM: pull credit byte with skb_pull_data() (git-fixes).\n- Bluetooth: SCO: check for codecs-\u003enum_codecs == 1 before assigning to sco_pi(sk)-\u003ecodec (git-fixes).\n- Bluetooth: SCO: fix sleeping under spinlock in sco_conn_ready (git-fixes).\n- Bluetooth: SCO: hold sk properly in sco_conn_ready (git-fixes).\n- Bluetooth: virtio_bt: clamp rx length before skb_put (git-fixes).\n- Bluetooth: virtio_bt: validate rx pkt_type header length (git-fixes).\n- btrfs: do not skip logging new dentries when logging a new name (git-fixes).\n- btrfs: reject root items with drop_progress and zero drop_level (git-fixes).\n- btrfs: replace BUG() with error handling in __btrfs_balance() (git-fixes).\n- can: mcp251x: add error handling for power enable in open and resume (stable-fixes).\n- can: raw: fix ro-\u003euniq use-after-free in raw_rcv() (git-fixes).\n- can: ucan: fix devres lifetime (git-fixes).\n- cdc-acm: new quirk for EPSON HMD (stable-fixes).\n- cgroup/cpuset: Fix incorrect change to effective_xcpus in partition_xcpus_del() (bsc#1241166).\n- cgroup/cpuset: Fix incorrect use of cpuset_update_tasks_cpumask() in update_cpumasks_hier() (bsc#1241166).\n- check-for-config-changes: Exclude CC_MS_EXTENSIONS.\n- check-for-config-changes: Exclude HAVE_CFI_ICALL_NORMALIZE_INTEGERS{,_RUSTC}.\n- checkpatch: add support for Assisted-by tag (stable-fixes).\n- comedi: dt2815: add hardware detection to prevent crash (stable-fixes).\n- cpufreq: intel_pstate: Drop Arrow Lake from 'scaling factor' list (bsc#1249104).\n- crypto: algif_aead - Fix minimum RX size check for decryption (git-fixes).\n- crypto: arm64/aes - Fix 32-bit aes_mac_update() arg treated as 64-bit (git-fixes).\n- crypto: atmel-aes - Fix 3-page memory leak in atmel_aes_buff_cleanup (git-fixes).\n- crypto: atmel-ecc - Release client on allocation failure (git-fixes).\n- crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path (git-fixes).\n- crypto: atmel-tdes - fix DMA sync direction (git-fixes).\n- crypto: authencesn - reject short ahash digests during instance creation (git-fixes).\n- crypto: ccp - copy IV using skcipher ivsize (git-fixes).\n- crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed (git-fixes).\n- crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed (git-fixes).\n- crypto: ccree - fix a memory leak in cc_mac_digest() (git-fixes).\n- crypto: hisilicon - Fix dma_unmap_single() direction (git-fixes).\n- crypto: jitterentropy - replace long-held spinlock with mutex (git-fixes).\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests (git-fixes).\n- crypto: qat - fix type mismatch in RAS sysfs show functions (git-fixes).\n- crypto: qat - use swab32 macro (git-fixes).\n- crypto: sa2ul - Fix AEAD fallback algorithm names (git-fixes).\n- crypto: simd - reject compat registrations without __ prefixes (git-fixes).\n- crypto: talitos - fix SEC1 32k ahash request limitation (git-fixes).\n- crypto: testmgr - Hide ENOENT errors (stable-fixes).\n- crypto: testmgr - Hide ENOENT errors better (git-fixes).\n- devres: fix missing node debug info in devm_krealloc() (git-fixes).\n- dm init: ensure device probing has finished in dm-mod.waitfor= (git-fixes).\n- dmaengine: dw-axi-dmac: Remove unnecessary return statement from void function (git-fixes).\n- dmaengine: mxs-dma: Fix missing return value from of_dma_controller_register() (git-fixes).\n- dpll: zl3073x: Add support to adjust phase (bsc#1255752).\n- dpll: zl3073x: Fix output pin phase adjustment sign (bsc#1255752).\n- dpll: zl3073x: Fix output pin registration (bsc#1255752).\n- dpll: zl3073x: fix REF_PHASE_OFFSET_COMP register width for some chip IDs (bsc#1255752).\n- dpll: zl3073x: Specify phase adjustment granularity for pins (bsc#1255752).\n- drm/amd/display: Add NULL check for integrated_info in clk_mgr_construct (git-fixes).\n- drm/amd/display: Allow DCE link encoder without AUX registers (git-fixes).\n- drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths (git-fixes).\n- drm/amd/display: Change dither policy for 10 bpc output back to dithering (git-fixes).\n- drm/amd/display: Correct logic check error for fastboot (git-fixes).\n- drm/amd/display: Disable 10-bit truncation and dithering on DCE 6.x (git-fixes).\n- drm/amd/display: Disable fastboot on DCE 6 too (stable-fixes).\n- drm/amd/display: Read EDID from VBIOS embedded panel info (git-fixes).\n- drm/amd/pm/ci: Clear EnabledForActivity field for memory levels (git-fixes).\n- drm/amd/pm/ci: Disable MCLK DPM on problematic CI ASICs (git-fixes).\n- drm/amd/pm/ci: Fill DW8 fields from SMC (git-fixes).\n- drm/amd/pm/ci: Fix powertune defaults for Hawaii 0x67B0 (git-fixes).\n- drm/amd/pm/ci: Use highest MCLK on CI when MCLK DPM is disabled (git-fixes).\n- drm/amd/pm/smu7: Add SCLK cap for quirky Hawaii board (git-fixes).\n- drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock (git-fixes).\n- drm/amd/pm: fix incorrect FeatureCtrlMask setting on smu v14.0.x (git-fixes).\n- drm/amdgpu/gfx6: Support harvested SI chips with disabled TCCs (v2) (git-fixes).\n- drm/amdgpu/gfx9: drop unnecessary 64-bit fence flag check in KIQ (stable-fixes).\n- drm/amdgpu/gfx10: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gfx11: look at the right prop for gfx queue priority (git-fixes).\n- drm/amdgpu/gmc: Fix AMDGPU_GART_PLACEMENT_LOW to not overlap with VRAM (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring (git-fixes).\n- drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring (git-fixes).\n- drm/amdgpu/pm: add missing revision check for CI (git-fixes).\n- drm/amdgpu/pm: align Hawaii mclk workaround with radeon (git-fixes).\n- drm/amdgpu/pm: drop SMU driver if version not matched messages (stable-fixes).\n- drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission (git-fixes).\n- drm/amdgpu/vce: Prevent partial address patches (stable-fixes).\n- drm/amdgpu/vcn3: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Avoid overflow on msg bound check (git-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (stable-fixes).\n- drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (stable-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v3.0 enc/dec rings (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.3 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v4.0.5 enc ring (git-fixes).\n- drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring (git-fixes).\n- drm/amdgpu: Add bounds checking to ib_{get,set}_value (stable-fixes).\n- drm/amdgpu: Add default case in DVI mode validation (git-fixes).\n- drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG (git-fixes).\n- drm/amdgpu: fix the idr allocation flags (git-fixes).\n- drm/amdgpu: fix zero-size GDS range init on RDNA4 (stable-fixes).\n- drm/amdgpu: gate VM CPU HDP flush on reset lock (stable-fixes).\n- drm/amdgpu: replace PASID IDR with XArray (git-fixes).\n- drm/amdgpu: Use SMUIO 15.0.0 offsets for TSC upper and lower count (stable-fixes).\n- drm/amdgpu: zero-initialize GART table on allocation (stable-fixes).\n- drm/amdkfd: Add upper bound check for num_of_nodes (stable-fixes).\n- drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure (stable-fixes).\n- drm/amdkfd: Make all TLB-flushes heavy-weight (stable-fixes).\n- drm/amdkfd: validate SVM ioctl nattr against buffer size (stable-fixes).\n- drm/arcpgu: fix device node leak (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check (git-fixes).\n- drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() (git-fixes).\n- drm/bridge: stm_lvds: Do not fail atomic_check on disabled connector (git-fixes).\n- drm/etnaviv: Fix armed job not being pushed to the DRM scheduler (git-fixes).\n- drm/exynos: remove bridge when component_add fails (git-fixes).\n- drm/fb-helper: Fix clipping when damage area spans a single scanline (git-fixes).\n- drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() (git-fixes).\n- drm/gma500/oaktrail_hdmi: fix i2c adapter leak on setup (git-fixes).\n- drm/gma500/oaktrail_lvds: fix hang on init failure (git-fixes).\n- drm/gma500/oaktrail_lvds: fix i2c adapter leaks on init (git-fixes).\n- drm/i915/dp: Fix VSC dynamic range signaling for RGB formats (git-fixes).\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat (git-fixes).\n- drm/i915/wm: Verify the correct plane DDB entry (git-fixes).\n- drm/i915: skip __i915_request_skip() for already signaled requests (git-fixes).\n- drm/imagination: Switch reset_reason fields from enum to u32 (git-fixes).\n- drm/komeda: fix integer overflow in AFBC framebuffer size check (git-fixes).\n- drm/loongson: Use managed KMS polling (git-fixes).\n- drm/msm/a6xx: Fix dumping A650+ debugbus blocks (git-fixes).\n- drm/msm/a6xx: Fix HLSQ register dumping (git-fixes).\n- drm/msm/a6xx: Use barriers while updating HFI Q headers (git-fixes).\n- drm/msm/dpu: fix mismatch between power and frequency (git-fixes).\n- drm/msm/dsi: add the missing parameter description (git-fixes).\n- drm/msm/dsi: fix bits_per_pclk (git-fixes).\n- drm/msm/dsi: fix hdisplay calculation for CMD mode panel (git-fixes).\n- drm/msm/dsi: rename MSM8998 DSI version from V2_2_0 to V2_0_0 (git-fixes).\n- drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata() (git-fixes).\n- drm/msm/shrinker: Fix can_block() logic (git-fixes).\n- drm/msm: add missing MODULE_DEVICE_ID definitions (git-fixes).\n- drm/nouveau: fix nvkm_device leak on aperture removal failure (git-fixes).\n- drm/nouveau: fix u32 overflow in pushbuf reloc bounds check (git-fixes).\n- drm/panel: boe-tv101wum-nl6: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: himax-hx83102: restore MODE_LPM after sending disable cmds (git-fixes).\n- drm/panel: sharp-ls043t1le01: make use of prepare_prev_first (git-fixes).\n- drm/panel: simple: Correct G190EAN01 prepare timing (git-fixes).\n- drm/panfrost: Fix wait_bo ioctl leaking positive return from dma_resv_wait_timeout() (git-fixes).\n- drm/panthor: Fix outdated function documentation (git-fixes).\n- drm/radeon: add missing revision check for CI (git-fixes).\n- drm/sun4i: backend: fix error pointer dereference (git-fixes).\n- drm/sun4i: Fix resource leaks (git-fixes).\n- drm/v3d: Handle error from drm_sched_entity_init() (git-fixes).\n- drm/vc4: Fix a memory leak in hang state error path (git-fixes).\n- drm/vc4: Fix memory leak of BO array in hang state (git-fixes).\n- drm/vc4: platform_get_irq_byname() returns an int (stable-fixes).\n- drm/vc4: Protect madv read in vc4_gem_object_mmap() with madv_lock (git-fixes).\n- drm/vc4: Release runtime PM reference after binding V3D (git-fixes).\n- drm/vram: remove DRM_VRAM_MM_FILE_OPERATIONS from docs (git-fixes).\n- drm/xe/bo: Fix bo leak on GGTT flag validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/bo: Fix bo leak on unaligned size validation in xe_bo_init_locked() (git-fixes).\n- drm/xe/debugfs: Correct printing of register whitelist ranges (git-fixes).\n- drm/xe/dma-buf: handle empty bo and UAF races (git-fixes).\n- drm/xe/gsc: Fix BO leak on error in query_compatibility_version() (git-fixes).\n- drm/xe/uapi: update used tracking kernel-doc (git-fixes).\n- drm/xe: Fix dma-buf attachment leak in xe_gem_prime_import() (git-fixes).\n- drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() (git-fixes).\n- dt-bindings: net: Fix Tegra234 MGBE PTP clock (git-fixes).\n- efi/capsule-loader: fix incorrect sizeof in phys array reallocation (git-fixes).\n- efi: pstore: Drop efivar lock when efi_pstore_open() returns with an error (git-fixes).\n- ext4: fix fsync(2) for nojournal mode (git-fixes).\n- ext4: make recently_deleted() properly work with lazy itable initialization (git-fixes).\n- ext4: reject mount if bigalloc with s_first_data_block != 0 (git-fixes).\n- extcon: ptn5150: handle pending IRQ events during system resume (git-fixes).\n- fbdev: matroxfb: Mark variable with __maybe_unused to avoid W=1 build break (git-fixes).\n- fbdev: offb: fix PCI device reference leak on probe failure (git-fixes).\n- fbdev: tdfxfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (stable-fixes).\n- fbdev: udlfb: add vm_ops to dlfb_ops_mmap to prevent use-after-free (stable-fixes).\n- fbdev: udlfb: avoid divide-by-zero on FBIOPUT_VSCREENINFO (git-fixes).\n- firmware: dmi: Correct an indexing error in dmi.h (git-fixes).\n- gpio: tegra: fix irq_release_resources calling enable instead of disable (git-fixes).\n- gtp: disable BH before calling udp_tunnel_xmit_skb() (git-fixes).\n- HID: alps: fix NULL pointer dereference in alps_raw_event() (git-fixes).\n- HID: asus: do not abort probe when not necessary (git-fixes).\n- HID: asus: make asus_resume adhere to linux kernel coding standards (git-fixes).\n- HID: core: clamp report_size in s32ton() to avoid undefined shift (stable-fixes).\n- HID: multitouch: Check to ensure report responses match the request (stable-fixes).\n- HID: playstation: Clamp num_touch_reports (git-fixes).\n- HID: quirks: add HID_QUIRK_ALWAYS_POLL for 8BitDo Pro 3 (stable-fixes).\n- HID: roccat: fix use-after-free in roccat_report_event (stable-fixes).\n- HID: usbhid: fix deadlock in hid_post_reset() (git-fixes).\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq (stable-fixes).\n- hv_sock: fix ARM64 support (git-fixes).\n- hwmon: (ads7871) Fix endianness bug in 16-bit register reads (git-fixes).\n- hwmon: (corsair-psu) Close HID device on probe errors (git-fixes).\n- hwmon: (lm63) Add locking to avoid TOCTOU (git-fixes).\n- hwmon: (ltc2992) Clamp threshold writes to hardware range (git-fixes).\n- hwmon: (ltc2992) Fix u32 overflow in power read path (git-fixes).\n- i2c: s3c24xx: check the size of the SMBUS message before using it (stable-fixes).\n- i2c: smbus: reject oversized block transfers in the common path (git-fixes).\n- i2c: stm32f7: reinit_completion() per transfer not per msg (git-fixes).\n- i2c: stub: Reject I2C block transfers with invalid length (git-fixes).\n- i3c: master: Fix error codes at send_ccc_cmd (git-fixes).\n- i3c: mipi-i3c-hci: fix IBI payload length calculation for final status (git-fixes).\n- ibmveth: Disable GSO for packets with small MSS (bsc#1265144).\n- ice: set max queues in alloc_etherdev_mqs() (git-fixes).\n- iio: adc: ad7768-1: fix one-shot mode data acquisition (git-fixes).\n- iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() (git-fixes).\n- iio: adc: ti-ads7950: use iio_push_to_buffers_with_ts_unaligned() (git-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max 16 Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: uinput - fix circular locking dependency with ff-core (git-fixes).\n- Input: uinput - take event lock when submitting FF request 'event' (stable-fixes).\n- Input: xpad - add support for BETOP BTP-KP50B/C controller's wireless mode (stable-fixes).\n- Input: xpad - add support for Razer Wolverine V3 Pro (stable-fixes).\n- intel_idle: add Clearwater Forest SoC support (jsc#PED-10383).\n- ipmi: Add limits to event and receive message requests (git-fixes).\n- ipmi: Check event message buffer response for bad data (git-fixes).\n- ipmi: ssif_bmc: change log level to dbg in irq callback (git-fixes).\n- ipmi: ssif_bmc: fix message desynchronization after truncated response (git-fixes).\n- ipmi: ssif_bmc: fix missing check for copy_to_user() partial failure (git-fixes).\n- irqchip/irq-pic32-evic: Address warning related to wrong printf() formatter (git-fixes).\n- kdump, documentation: describe craskernel CMA reservation (jsc#PED-7249).\n- KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (git-fixes).\n- KVM: SVM: Fix a missing kunmap_local() in sev_gmem_post_populate() (git-fixes).\n- KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN (git-fixes).\n- KVM: SVM: Mark VMCB_PERM_MAP as dirty on nested VMRUN (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86/mmu: Retry fault before acquiring mmu_lock if mapping is changing (bsc#1253122).\n- KVM: x86/xen: Fix cleanup logic in emulation of Xen schedop poll hypercalls (git-fixes).\n- KVM: x86: check for nEPT/nNPT in slow flush hypercalls (git-fixes).\n- KVM: x86: Fix shadow paging use-after-free due to unexpected GFN (git-fixes).\n- KVM: x86: hyper-v: Validate all GVAs during PV TLB flush (git-fixes).\n- KVM: x86: Ignore cpuid faulting in SMM (git-fixes).\n- leds: lgm-sso: Remove duplicate assignments for priv-\u003emmap (git-fixes).\n- leds: qcom-lpg: Check for array overflow when selecting the high resolution (stable-fixes).\n- lib/hexdump: print_hex_dump_bytes() calls print_hex_dump_debug() (git-fixes).\n- md/raid1: fix the comparing region of interval tree (bsc#1261555).\n- md/raid1: serialize overlap io for writemostly disk (bsc#1261555).\n- media: amphion: Fix race between m2m job_abort and device_run (git-fixes).\n- media: as102: fix to not free memory after the device is registered in as102_usb_probe() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for handle_dynamic_resolution_change() (git-fixes).\n- media: chips-media: wave5: add missing spinlock protection for send_eos_event() (git-fixes).\n- media: chips-media: wave5: fix a potential memory leak in wave5_vdi_init() (git-fixes).\n- media: dib8000: avoid division by 0 in dib8000_set_dds() (git-fixes).\n- media: em28xx: fix use-after-free in em28xx_v4l2_open() (git-fixes).\n- media: hackrf: fix to not free memory after the device is registered in hackrf_probe() (git-fixes).\n- media: i2c: imx219: Check return value of devm_gpiod_get_optional() in imx219_probe() (git-fixes).\n- media: i2c: imx412: Assert reset GPIO during probe (git-fixes).\n- media: i2c: ov08d10: fix image vertical start setting (git-fixes).\n- media: i2c: ov8856: free control handler on error in ov8856_init_controls() (git-fixes).\n- media: intel/ipu6: fix error pointer dereference (git-fixes).\n- media: mtk-jpeg: fix use-after-free in release path due to uncancelled work (git-fixes).\n- media: nxp: imx8-isi: Reduce minimum queued buffers from 2 to 0 (git-fixes).\n- media: omap3isp: drop the use count of v4l2 pipeline (git-fixes).\n- media: pci: zoran: fix potential memory leak in zoran_probe() (git-fixes).\n- media: rc: streamzap: Error handling in probe (git-fixes).\n- media: rc: xbox_remote: heed DMA restrictions (git-fixes).\n- media: saa7164: add ioremap return checks and cleanups (git-fixes).\n- media: staging: imx: configure src_mux in csi_start (git-fixes).\n- media: staging: imx: request mbus_config in csi_start (git-fixes).\n- media: uvcvideo: Enable VB2_DMABUF for metadata stream (git-fixes).\n- media: videobuf2: Set vma_flags in vb2_dma_sg_mmap (git-fixes).\n- media: vidtv: fix nfeeds state corruption on start_streaming failure (git-fixes).\n- media: vidtv: fix NULL pointer dereference in vidtv_channel_pmt_match_sections (git-fixes).\n- media: vidtv: fix pass-by-value structs causing MSAN warnings (git-fixes).\n- memory: tegra30-emc: Fix dll_change check (git-fixes).\n- memory: tegra124-emc: Fix dll_change check (git-fixes).\n- mfd: mc13xxx-core: Fix memory leak in mc13xxx_add_subdevice_pdata() (git-fixes).\n- mkspec: Add signature to source list only when it exists.\n- mmc: sdhci-of-dwcmshc: Disable clock before DLL configuration (git-fixes).\n- mmc: vub300: fix NULL-deref on disconnect (git-fixes).\n- modpost: Amend ppc64 save/restfpr symnames for -Os build (bsc#1215199).\n- mtd: docg3: Convert to platform remove callback returning void (stable-fixes).\n- mtd: docg3: fix use-after-free in docg3_release() (git-fixes).\n- mtd: parsers: ofpart: call of_node_get() for dedicated subpartitions (git-fixes).\n- mtd: parsers: ofpart: call of_node_put() only in ofpart_fail path (git-fixes).\n- mtd: physmap_of_gemini: Fix disabled pinctrl state check (git-fixes).\n- mtd: rawnand: sunxi: fix sunxi_nfc_hw_ecc_read_extra_oob (git-fixes).\n- mtd: spi-nor: core: correct the op.dummy.nbytes when check read operations (git-fixes).\n- mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() (git-fixes).\n- mtd: spi-nor: sst: Factor out common write operation to `sst_nor_write_data()` (stable-fixes).\n- mtd: spi-nor: sst: Fix SST write failure (git-fixes).\n- mtd: spi-nor: sst: Fix write enable before AAI sequence (git-fixes).\n- mtd: spi-nor: swp: check SR_TB flag when getting tb_mask (git-fixes).\n- net/rds: reset op_nents when zerocopy page pin fails (bsc#1265626).\n- net/sched: cls_fw: fix NULL dereference of 'old' filters before change() (git-fixes).\n- net: gro: don't merge zcopy skbs (git-fixes).\n- net: mana: Add MAC address to vPort logs and clarify error messages (git-fixes).\n- net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() (git-fixes).\n- net: mana: Don't overwrite port probe error with add_adev result (git-fixes).\n- net: mana: Fix crash from unvalidated SHM offset read from BAR0 during FLR (bsc#1265846).\n- net: mana: Fix EQ leak in mana_remove on NULL port (git-fixes).\n- net: mana: Fix RX skb truesize accounting (bsc#1248754).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: Guard mana_remove against double invocation (git-fixes).\n- net: mana: hardening: Validate adapter_mtu from MANA_QUERY_DEV_CONFIG (git-fixes).\n- net: mana: hardening: Validate doorbell ID from GDMA_REGISTER_DEVICE response (git-fixes).\n- net: mana: Init gf_stats_work before potential error paths in probe (git-fixes).\n- net: mana: Init link_change_work before potential error paths in probe (git-fixes).\n- net: mana: remove double CQ cleanup in mana_create_rxq error path (git-fixes).\n- net: mana: Set default number of queues to 16 (bsc#1261648).\n- net: mana: Skip WQ object destruction for uninitialized RXQ (git-fixes).\n- net: mana: Use at least SZ_4K in doorbell ID range check (git-fixes).\n- net: mana: Use pci_name() for debugfs directory naming (git-fixes).\n- net: phy: dp83869: fix setting CLK_O_SEL field (git-fixes).\n- net: stmmac: Fix PTP ref clock for Tegra234 (git-fixes).\n- net: usb: asix: ax88772: re-add usbnet_link_change() in phylink callbacks (git-fixes).\n- net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete() (git-fixes).\n- net: usb: rtl8150: fix use-after-free in rtl8150_start_xmit() (git-fixes).\n- net: usb: rtl8150: free skb on usb_submit_urb() failure in xmit (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix ucc_hdlc_remove (git-fixes).\n- net: wan: fsl_ucc_hdlc: fix uhdlc_memclean (git-fixes).\n- net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean (git-fixes).\n- NFC: digital: Bounds check NFC-A cascade depth in SDD response handler (git-fixes).\n- nfc: llcp: add missing return after LLCP_CLOSED checks (git-fixes).\n- nfc: pn533: allocate rx skb before consuming bytes (git-fixes).\n- nfc: s3fwrn5: allocate rx skb before consuming bytes (git-fixes).\n- NFC: trf7970a: Ignore antenna noise when checking for RF field (git-fixes).\n- nvme-auth: Include SC_C in RVAL controller hash (bsc#1260428).\n- nvme-fabrics: use kfree_sensitive() for DHCHAP secrets (git-fixes).\n- nvme-loop: do not cancel I/O and admin tagset during ctrl reset/shutdown (bsc#1262709).\n- nvme-pci: cap queue creation to used queues (git-fixes).\n- nvme-pci: ensure we're polling a polled queue (git-fixes).\n- nvme: Allow reauth from sysfs (bsc#1259672).\n- nvme: Expose the tls_configured sysfs for secure concat connections (bsc#1259672).\n- nvme: expose TLS mode (bsc#1259672).\n- nvme: fix PCIe subsystem reset controller state transition (bsc#1261738).\n- nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers (git-fixes).\n- ocfs2: fix possible deadlock between unlink and dio_end_io_write (bsc#1258718).\n- ocfs2: split transactions in dio completion to avoid credit exhaustion (bsc#1258718).\n- Partial revert 'x86/xen: fix balloon target initialization for PVH dom0' (bsc#1262599).\n- PCI/AER: Clear only error bits in PCIe Device Status (git-fixes).\n- PCI/AER: Stop ruling out unbound devices as error source (git-fixes).\n- PCI: dwc: Apply ECRC workaround to DesignWare 5.00a as well (git-fixes).\n- PCI: Enable AtomicOps only if Root Port supports them (git-fixes).\n- PCI: endpoint: pci-epf-ntb: Remove duplicate resource teardown (git-fixes).\n- PCI: hv: Set default NUMA node to 0 for devices without affinity info (git-fixes).\n- PCI: mediatek-gen3: Prevent leaking IRQ domains when IRQ not found (git-fixes).\n- PCI: tegra194: Allow system suspend when the Endpoint link is not up (git-fixes).\n- PCI: tegra194: Disable direct speed change for Endpoint mode (git-fixes).\n- PCI: tegra194: Disable LTSSM after transition to Detect on surprise link down (git-fixes).\n- PCI: tegra194: Disable PERST# IRQ only in Endpoint mode (git-fixes).\n- PCI: tegra194: Fix polling delay for L2 state (git-fixes).\n- PCI: tegra194: Increase LTSSM poll time on surprise link down (git-fixes).\n- PCI: tegra194: Set LTR message request before PCIe link up in Endpoint mode (git-fixes).\n- PCI: tegra194: Use devm_gpiod_get_optional() to parse 'nvidia,refclk-select' (git-fixes).\n- PCI: tegra194: Use DWC IP core version (git-fixes).\n- pinctrl: abx500: Fix type of 'argument' variable (git-fixes).\n- pinctrl: Fix spelling problem (git-fixes).\n- pinctrl: intel: Fix the revision for new features (1kOhm PD, HW debouncer) (stable-fixes).\n- pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' (git-fixes).\n- pinctrl: pic32: use consistent spacing around '+' (git-fixes).\n- pinctrl: pinctrl-pic32: Fix resource leak (git-fixes).\n- platform/chrome: chromeos_tbmc: Drop wakeup source on remove (git-fixes).\n- platform/surface: surfacepro3_button: Drop wakeup source on remove (git-fixes).\n- platform/x86/amd: pmc: Add Thinkpad L14 Gen3 to quirk_s2idle_bug (stable-fixes).\n- platform/x86/intel-uncore-freq: Handle autonomous UFS status bit (git-fixes).\n- platform/x86/intel: power-domains: Add Clearwater Forest support (jsc#PED-16221).\n- platform/x86: dell-wmi-sysman: bound enumeration string aggregation (git-fixes).\n- platform/x86: dell_rbu: avoid uninit value usage in packet_size_write() (git-fixes).\n- platform/x86: hp-wmi: Ignore backlight and FnLock events (stable-fixes).\n- platform/x86: ISST: Add Clearwater Forest to support list (jsc#PED-16221).\n- platform/x86: panasonic-laptop: Fix OPTD notifier registration and cleanup (git-fixes).\n- power: supply: axp288_charger: Do not cancel work before initializing it (git-fixes).\n- power: supply: max17042: avoid overflow when determining health (git-fixes).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/crash: fix backup region offset update to elfcorehdr (bsc#1259535).\n- powerpc/crash: Update backup region offset in elfcorehdr on memory hotplug (bsc#1259535).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- RDMA/mana: Fix error unwind in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Fix mana_destroy_wq_obj() cleanup in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() (git-fixes).\n- RDMA/mana: Validate rx_hash_key_len (git-fixes).\n- RDMA/mana_ib: cleanup the usage of mana_gd_send_request() (git-fixes).\n- RDMA/mana_ib: Disable RX steering on RSS QP destroy (git-fixes).\n- RDMA/mana_ib: Support memory windows (git-fixes).\n- regulator: act8945a: fix OF node reference imbalance (git-fixes).\n- regulator: bd9571mwv: fix OF node reference imbalance (git-fixes).\n- regulator: max77650: fix OF node reference imbalance (git-fixes).\n- regulator: mt6357: fix OF node reference imbalance (git-fixes).\n- remoteproc: xlnx: Only access buffer information if IPI is buffered (git-fixes).\n- Revert 'ALSA: usb: Increase volume range that triggers a warning' (git-fixes).\n- rtc: abx80x: Disable alarm feature if no interrupt attached (git-fixes).\n- rtc: ntxec: fix OF node reference imbalance (git-fixes).\n- s390/dasd: Copy detected format information to secondary device (bsc#1259995).\n- s390/dasd: Fix gendisk parent after copy pair swap (bsc#1259995).\n- s390/dasd: Move quiesce state with pprc swap (bsc#1259995).\n- sched/balancing: Switch the 'DEFINE_SPINLOCK(balancing)' spinlock into an 'atomic_t sched_balance_running' flag\n  (bsc#1253754).\n- sched/fair: Change likelyhood of nohz.nr_cpus (bsc#1234634 bsc#1258961).\n- sched/fair: Have SD_SERIALIZE affect newidle balancing (bsc#1253754).\n- sched/fair: Move checking for nohz cpus after time check (bsc#1234634 bsc#1258961).\n- sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead (bsc#1234634 bsc#1258961).\n- sched/fair: Skip sched_balance_running cmpxchg when balance is not due (bsc#1253754).\n- scsi: lpfc: Add clean up of aborted NVMe commands during PCI fcn reset (bsc#1262019).\n- scsi: lpfc: Add log messages to fabric login error labels (bsc#1262019).\n- scsi: lpfc: Add PCI ID support for LPe42100 series adapters (bsc#1262019).\n- scsi: lpfc: Add REG_VFI mailbox cmd error handling (bsc#1262019).\n- scsi: lpfc: Break out of IRQ affinity assignment when mask reaches nr_cpu_ids (bsc#1262019).\n- scsi: lpfc: Check ASIC_ID register to aid diagnostics during failed fw updates (bsc#1262019).\n- scsi: lpfc: Cleanup error exit paths in lpfc_fdmi_cmd() and associated messages (bsc#1262019).\n- scsi: lpfc: ELIMINATE kernel-doc warnings in lpfc.h (bsc#1262019).\n- scsi: lpfc: Fix incorrect txcmplq_cnt during cleanup in lpfc_sli_abort_ring() (bsc#1262019).\n- scsi: lpfc: Introduce 128G link speed selection and support (bsc#1262019).\n- scsi: lpfc: Log discarded and insufficient RQE buffer events (bsc#1262019).\n- scsi: lpfc: Log MCQE contents for mbox commands with no context (bsc#1262019).\n- scsi: lpfc: Properly set WC for DPP mapping (bsc#1262019).\n- scsi: lpfc: Reduce pointer chasing when accessing vmid_flag (bsc#1262019).\n- scsi: lpfc: Remove deprecated PBDE feature (bsc#1262019).\n- scsi: lpfc: Remove unnecessary ndlp kref get in lpfc_check_nlp_post_devloss (bsc#1262019).\n- scsi: lpfc: Restrict first burst to non-FCoE and SLI4 adapters only (bsc#1262019).\n- scsi: lpfc: Select mailbox rq_create cmd version based on SLI4 if_type (bsc#1262019).\n- scsi: lpfc: Update class of service bit field to 3 bits for WQE submissions (bsc#1262019).\n- scsi: lpfc: Update construction of SGL when XPSGL is enabled (bsc#1262019).\n- scsi: lpfc: Update copyright year string for 2026 (bsc#1262019).\n- scsi: lpfc: Update log message when ndlp kref get is unsuccessful (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 14.4.0.14 (bsc#1262019).\n- scsi: lpfc: Update lpfc version to 15.0.0.0 (bsc#1262019).\n- scsi: lpfc: Update outdated comment for renamed lpfc_freenode() (bsc#1262019).\n- scsi: lpfc: Use min_t() instead of min() in lpfc_sli4_driver_resource_setup (bsc#1262019).\n- scsi: storvsc: Handle PERSISTENT_RESERVE_IN truncation for Hyper-V vFC (git-fixes).\n- scsi: target: iscsi: validate CHAP_R length before base64 decode (bsc#1265449).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669 ltc#212590).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669 ltc#212590).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- serial: 8250: Add serial8250_handle_irq_locked() (bsc#1262480).\n- serial: 8250: Protect LCR write in shutdown (bsc#1262480).\n- serial: 8250_dw: Avoid unnecessary LCR writes (bsc#1262480).\n- serial: 8250_dw: Ensure BUSY is deasserted (bsc#1262480).\n- serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling (bsc#1262480).\n- serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm (bsc#1262480).\n- soc/tegra: cbb: Set ERD on resume for err interrupt (git-fixes).\n- soc: qcom: aoss: compare against normalized cooling state (git-fixes).\n- soc: qcom: llcc: fix v1 SB syndrome register offset (git-fixes).\n- sound: ua101: fix division by zero at probe (git-fixes).\n- soundwire: bus: demote UNATTACHED state warnings to dev_dbg() (git-fixes).\n- soundwire: cadence: Clear message complete before signaling waiting thread (git-fixes).\n- spi: at91-usart: fix controller deregistration (git-fixes).\n- spi: atmel: fix controller deregistration (git-fixes).\n- spi: cadence: fix controller deregistration (git-fixes).\n- spi: fix controller cleanup() documentation (git-fixes).\n- spi: fix misleading controller deregistration kernel-doc (git-fixes).\n- spi: fix misleading controller registration kernel-doc (git-fixes).\n- spi: fsl-qspi: Use reinit_completion() for repeated operations (git-fixes).\n- spi: hisi-kunpeng: prevent infinite while() loop in hisi_spi_flush_fifo (git-fixes).\n- spi: imx: fix runtime pm leak on probe deferral (git-fixes).\n- spi: imx: fix use-after-free on unbind (git-fixes).\n- spi: microchip-core-qspi: fix controller deregistration (git-fixes).\n- spi: microchip-core-qspi: Use helper function devm_clk_get_enabled() (stable-fixes).\n- spi: mpc52xx: fix use-after-free on unbind (git-fixes).\n- spi: mtk-nor: fix controller deregistration (git-fixes).\n- spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback (git-fixes).\n- spi: omap2-mcspi: fix controller deregistration (git-fixes).\n- spi: orion: fix clock imbalance on registration failure (git-fixes).\n- spi: orion: fix runtime pm leak on unbind (git-fixes).\n- spi: rockchip: fix controller deregistration (git-fixes).\n- spi: rspi: fix controller deregistration (git-fixes).\n- spi: sh-hspi: fix controller deregistration (git-fixes).\n- spi: spi-ti-qspi: Convert to platform remove callback returning void (stable-fixes).\n- spi: sprd: fix controller deregistration (git-fixes).\n- spi: sun4i: fix controller deregistration (git-fixes).\n- spi: sun4i: switch to use modern name (stable-fixes).\n- spi: syncuacer: fix controller deregistration (git-fixes).\n- spi: synquacer: switch to use modern name (stable-fixes).\n- spi: uniphier: fix controller deregistration (git-fixes).\n- spi: uniphier: Simplify clock handling with devm_clk_get_enabled() (stable-fixes).\n- spi: uniphier: switch to use modern name (stable-fixes).\n- spi: zynq-qspi: switch to use modern name (stable-fixes).\n- spi: zynqmp-gqspi: fix controller deregistration (git-fixes).\n- staging: media: atomisp: Disallow all private IOCTLs (git-fixes).\n- staging: rtl8723bs: initialize le_tmp64 in rtw_BIP_verify() (git-fixes).\n- staging: sm750fb: fix division by zero in ps_to_hz() (git-fixes).\n- staging: vme_user: added bound check to geoid (stable-fixes).\n- staging: vme_user: fix root device leak on init failure (git-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- tg3: replace placeholder MAC address with device property (git-fixes).\n- thermal/drivers/spear: Fix error condition for reading st,thermal-flags (git-fixes).\n- thermal/drivers/sprd: Fix raw temperature clamping in sprd_thm_rawdata_to_temp (git-fixes).\n- thermal/drivers/sprd: Fix temperature clamping in sprd_thm_temp_to_rawdata (git-fixes).\n- tpm: avoid -Wunused-but-set-variable (git-fixes).\n- tpm: tpm_tis: add error logging for data transfer (git-fixes).\n- tpm: tpm_tis: stop transmit if retries are exhausted (git-fixes).\n- tty: tty_io: update timestamps on all device nodes (bsc#1262020).\n- unshare: fix unshare_fs() handling (git-fixes).\n- USB: cdc-acm: Add quirks for Yoga Book 9 14IAH10 INGENIC touchscreen (stable-fixes).\n- usb: chipidea: core: allow ci_irq_handler() handle both ID and VBUS change (git-fixes).\n- usb: chipidea: otg: not wait vbus drop if use role_switch (git-fixes).\n- USB: core: add NO_LPM quirk for Razer Kiyo Pro webcam (stable-fixes).\n- usb: gadget: dummy_hcd: fix premature URB completion when ZLP follows partial transfer (stable-fixes).\n- usb: gadget: f_ncm: validate minimum block_len in ncm_unwrap_ntb() (git-fixes).\n- usb: gadget: f_phonet: fix skb frags[] overflow in pn_rx_complete() (stable-fixes).\n- usb: gadget: f_uac1_legacy: validate control request size (stable-fixes).\n- usb: gadget: renesas_usb3: validate endpoint index in standard request handlers (git-fixes).\n- USB: omap_udc: DMA: Don't enable burst 4 mode (git-fixes).\n- usb: port: add delay after usb_hub_set_port_power() (git-fixes).\n- usb: quirks: add DELAY_INIT quirk for another Silicon Motion flash drive (stable-fixes).\n- USB: serial: io_edgeport: add support for Blackbox IC135A (stable-fixes).\n- USB: serial: option: add MeiG Smart SRM825WN (stable-fixes).\n- USB: serial: option: add support for Rolling Wireless RW135R-GL (stable-fixes).\n- USB: serial: option: add Telit Cinterion FN990A MBIM composition (stable-fixes).\n- USB: serial: option: add Telit Cinterion LE910Cx compositions (stable-fixes).\n- usb: storage: Expand range of matched versions for VL817 quirks entry (stable-fixes).\n- usb: typec: tcpm: reset internal port states on soft reset AMS (git-fixes).\n- usb: ulpi: fix memory leak on ulpi_register() error paths (git-fixes).\n- usb: usblp: fix heap leak in IEEE 1284 device ID via short response (stable-fixes).\n- usb: usblp: fix uninitialized heap leak via LPGETSTATUS ioctl (stable-fixes).\n- usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable() (git-fixes).\n- usbip: validate number_of_packets in usbip_pack_ret_submit() (git-fixes).\n- virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (git-fixes).\n- virt: tdx-guest: Return error for GetQuote failures (git-fixes).\n- wifi: ath5k: do not access array OOB (git-fixes).\n- wifi: ath9k: Fix typo (git-fixes).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: ath11k: skip status ring entry processing (stable-fixes).\n- wifi: ath11k: Use dma_alloc_noncoherent for rx_tid buffer allocation (stable-fixes).\n- wifi: ath12k: fix leak in some ath12k_wmi_xxx() functions (git-fixes).\n- wifi: b43: enforce bounds check on firmware key index in b43_rx() (git-fixes).\n- wifi: b43legacy: enforce bounds check on firmware key index in RX path (git-fixes).\n- wifi: brcmfmac: Fix error pointer dereference (git-fixes).\n- wifi: brcmfmac: validate bsscfg indices in IF events (stable-fixes).\n- wifi: brcmsmac: Fix dma_free_coherent() size (git-fixes).\n- wifi: cw1200: Revert 'Fix locking in error paths' (git-fixes).\n- wifi: libertas: notify firmware load wait on disconnect (git-fixes).\n- wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path (git-fixes).\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper (stable-fixes).\n- wifi: mac80211: drop stray 'static' from fast-RX rx_result (git-fixes).\n- wifi: mac80211: handle VHT EXT NSS in ieee80211_determine_our_sta_mode() (git-fixes).\n- wifi: mac80211: remove station if connection prep fails (git-fixes).\n- wifi: mac80211: use safe list iteration in radar detect work (git-fixes).\n- wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor (stable-fixes).\n- wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling (git-fixes).\n- wifi: mt76: mt7615: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7915: fix use-after-free bugs in mt7915_mac_dump_work() (git-fixes).\n- wifi: mt76: mt7915: fix use_cts_prot support (git-fixes).\n- wifi: mt76: mt7921: fix 6GHz regulatory update on connection (git-fixes).\n- wifi: mt76: mt7921: fix a potential clc buffer length underflow (git-fixes).\n- wifi: mt76: mt7921: fix ROC abort flow interruption in mt7921_roc_work (git-fixes).\n- wifi: mt76: mt7921: Reset ampdu_state state in case of failure in mt76_connac2_tx_check_aggr() (git-fixes).\n- wifi: mt76: mt7925: fix incorrect length field in txpower command (git-fixes).\n- wifi: mt76: mt7996: fix FCS error flag check in RX descriptor (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_uni_event (git-fixes).\n- wifi: mwifiex: Fix memory leak in mwifiex_11n_aggregate_pkt() (git-fixes).\n- wifi: nl80211: fix NL80211_PMSR_FTM_REQ_ATTR_FTMS_PER_BURST usage (git-fixes).\n- wifi: nl80211: require admin perm on SET_PMK / DEL_PMK (git-fixes).\n- wifi: rsi: fix kthread lifetime race between self-exit and external-stop (git-fixes).\n- wifi: rt2x00usb: fix devres lifetime (git-fixes).\n- wifi: rtlwifi: pci: fix possible use-after-free caused by unfinished irq_prepare_bcn_tasklet (git-fixes).\n- wifi: rtw88: check for PCI upstream bridge existence (git-fixes).\n- wifi: rtw88: fix device leak on probe failure (git-fixes).\n- wifi: rtw89: phy: fix uninitialized variable access in rtw89_phy_cfo_set_crystal_cap() (git-fixes).\n- wifi: wl1251: validate packet IDs before indexing tx_frames (stable-fixes).\n- workqueue: Break up enum definitions and give names to the types (bsc#1260522).\n- workqueue: Clean up enum work_bits and related constants (bsc#1260522).\n- workqueue: Factor out work_grab_pending() from __cancel_work_sync() (bsc#1260522).\n- workqueue: Fix UBSAN 'subtraction overflow' error in shift_and_mask() (bsc#1260522).\n- workqueue: Implement disable/enable for (delayed) work items (bsc#1260522).\n- workqueue: Introduce work_cancel_flags (bsc#1260522).\n- workqueue: Make @flags handling consistent across set_work_data() and friends (bsc#1260522).\n- workqueue: Preserve OFFQ bits in cancel[_sync] paths (bsc#1260522).\n- workqueue: Rename __cancel_work_timer() to __cancel_timer_sync() (bsc#1260522).\n- workqueue: Reorganize flush and cancel[_sync] functions (bsc#1260522).\n- x86/boot/64: Clear most of CR4 in startup_64(), except PAE, MCE and LA57 (git-fixes).\n- x86/boot/sev: Avoid shared GHCB page for early memory acceptance (git-fixes).\n- x86/boot: Don't add the EFI stub to targets, again (git-fixes).\n- x86/boot: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- x86/CPU/AMD: Add models 0x60-0x6f to the Zen5 range (bsc#1263255).\n- x86/CPU/AMD: Add X86_FEATURE_ZEN6 (bsc#1263255).\n- x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask (git-fixes).\n- x86/cpufeatures: Free up unused feature bits (bsc#1263255).\n- x86/fred: Remove ENDBR64 from FRED entry points (git-fixes).\n- x86: KVM: Advertise CPUIDs for new instructions in Clearwater Forest (jsc#PED-16245).\n- X.509: Fix out-of-bounds access when parsing extensions (git-fixes).\n- Xarray: do not return sibling entries from xas_find_marked() (bsc#1263815).\n- xfrm: esp: avoid in-place decrypt on shared skb frags (bsc#1264449).\n","status":"published","published":"2026-06-30T10:03:11Z","modified":"2026-07-01T09:59:29.1306508Z","updated_at":"2026-11-02T15:54:03.080707Z"},{"id":"USN-8567-1","title":"linux, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320)\n","status":"published","published":"2026-07-20T15:36:35Z","modified":"2026-11-07T01:46:48.030854859Z","updated_at":"2026-11-07T01:56:38.538236Z"},{"id":"USN-8574-1","title":"linux-gcp-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-21T09:51:58Z","modified":"2026-11-09T12:46:41.603455464Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8574-2","title":"linux-fips, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T07:48:36Z","modified":"2026-11-09T12:48:51.609882158Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8574-3","title":"linux-ibm, linux-ibm-6.8, linux-nvidia-tegra, linux-xilinx vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-28T07:23:25Z","modified":"2026-11-09T12:49:17.012782847Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-1","title":"linux-oracle-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-23T07:57:09Z","modified":"2026-11-09T12:46:39.626735177Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-2","title":"linux-aws vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-24T10:14:09Z","modified":"2026-11-09T12:46:40.833371554Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-3","title":"linux-aws-6.8, linux-aws-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-28T07:25:50Z","modified":"2026-11-09T12:49:11.651297869Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8596-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23226, CVE-2026-23227, CVE-2026-23244, CVE-2026-23245,\nCVE-2026-23246, CVE-2026-23253, CVE-2026-23255, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23276, CVE-2026-23277, CVE-2026-23279,\nCVE-2026-23281, CVE-2026-23284, CVE-2026-23285, CVE-2026-23286,\nCVE-2026-23287, CVE-2026-23289, CVE-2026-23290, CVE-2026-23291,\nCVE-2026-23292, CVE-2026-23293, CVE-2026-23296, CVE-2026-23298,\nCVE-2026-23300, CVE-2026-23302, CVE-2026-23303, CVE-2026-23304,\nCVE-2026-23306, CVE-2026-23307, CVE-2026-23308, CVE-2026-23310,\nCVE-2026-23312, CVE-2026-23313, CVE-2026-23315, CVE-2026-23317,\nCVE-2026-23318, CVE-2026-23319, CVE-2026-23321, CVE-2026-23324,\nCVE-2026-23325, CVE-2026-23330, CVE-2026-23334, CVE-2026-23335,\nCVE-2026-23336, CVE-2026-23339, CVE-2026-23340, CVE-2026-23343,\nCVE-2026-23347, CVE-2026-23352, CVE-2026-23356, CVE-2026-23357,\nCVE-2026-23359, CVE-2026-23360, CVE-2026-23361, CVE-2026-23362,\nCVE-2026-23363, CVE-2026-23364, CVE-2026-23365, CVE-2026-23367,\nCVE-2026-23368, CVE-2026-23369, CVE-2026-23370, CVE-2026-23372,\nCVE-2026-23374, CVE-2026-23375, CVE-2026-23378, CVE-2026-23379,\nCVE-2026-23381, CVE-2026-23382, CVE-2026-23383, CVE-2026-23386,\nCVE-2026-23387, CVE-2026-23388, CVE-2026-23389, CVE-2026-23391,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439,\nCVE-2026-23440, CVE-2026-23441, CVE-2026-23442, CVE-2026-23444,\nCVE-2026-23446, CVE-2026-23447, CVE-2026-23448, CVE-2026-23449,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23456, CVE-2026-23457,\nCVE-2026-23458, CVE-2026-23460, CVE-2026-23461, CVE-2026-23462,\nCVE-2026-23463, CVE-2026-23464, CVE-2026-23465, CVE-2026-23468,\nCVE-2026-23470, CVE-2026-23474, CVE-2026-23475, CVE-2026-31389,\nCVE-2026-31391, CVE-2026-31392, CVE-2026-31393, CVE-2026-31394,\nCVE-2026-31396, CVE-2026-31399, CVE-2026-31400, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31412, CVE-2026-31413, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31421, CVE-2026-31422,\nCVE-2026-31423, CVE-2026-31424, CVE-2026-31425, CVE-2026-31426,\nCVE-2026-31427, CVE-2026-31428, CVE-2026-31429, CVE-2026-31430,\nCVE-2026-31432, CVE-2026-31433, CVE-2026-31434, CVE-2026-31438,\nCVE-2026-31439, CVE-2026-31440, CVE-2026-31441, CVE-2026-31446,\nCVE-2026-31447, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53354,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T08:06:00Z","modified":"2026-11-09T12:48:44.712103783Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8606-1","title":"linux-azure, linux-azure-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - 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  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43378, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43383, CVE-2026-43384, CVE-2026-43386,\nCVE-2026-43387, CVE-2026-43395, CVE-2026-43397, CVE-2026-43405,\nCVE-2026-43406, CVE-2026-43407, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43414,\nCVE-2026-43415, CVE-2026-43419, CVE-2026-43420, CVE-2026-43421,\nCVE-2026-43424, CVE-2026-43425, CVE-2026-43426, CVE-2026-43427,\nCVE-2026-43428, CVE-2026-43429, CVE-2026-43430, CVE-2026-43432,\nCVE-2026-43436, CVE-2026-43437, CVE-2026-43439, CVE-2026-43441,\nCVE-2026-43445, CVE-2026-43448, CVE-2026-43449, CVE-2026-43450,\nCVE-2026-43451, CVE-2026-43452, CVE-2026-43453, CVE-2026-43455,\nCVE-2026-43456, CVE-2026-43457, CVE-2026-43458, CVE-2026-43459,\nCVE-2026-43466, CVE-2026-43467, CVE-2026-43468, CVE-2026-43469,\nCVE-2026-43471, CVE-2026-43472, CVE-2026-43473, CVE-2026-43475,\nCVE-2026-43476, CVE-2026-43480, CVE-2026-43483, CVE-2026-43484,\nCVE-2026-43488, CVE-2026-43490, CVE-2026-43491, CVE-2026-43492,\nCVE-2026-43493, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497,\nCVE-2026-43499, CVE-2026-43501, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45855, CVE-2026-45856, CVE-2026-45857, CVE-2026-45858,\nCVE-2026-45859, CVE-2026-45860, CVE-2026-45861, CVE-2026-45862,\nCVE-2026-45864, CVE-2026-45865, CVE-2026-45866, CVE-2026-45867,\nCVE-2026-45868, CVE-2026-45869, CVE-2026-45870, CVE-2026-45871,\nCVE-2026-45872, CVE-2026-45873, CVE-2026-45875, CVE-2026-45877,\nCVE-2026-45878, CVE-2026-45879, CVE-2026-45880, CVE-2026-45881,\nCVE-2026-45882, CVE-2026-45883, CVE-2026-45884, CVE-2026-45885,\nCVE-2026-45886, CVE-2026-45890, CVE-2026-45891, CVE-2026-45893,\nCVE-2026-45895, CVE-2026-45899, CVE-2026-45902, CVE-2026-45904,\nCVE-2026-45905, CVE-2026-45910, CVE-2026-45911, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45920, CVE-2026-45921,\nCVE-2026-45923, CVE-2026-45924, CVE-2026-45928, CVE-2026-45935,\nCVE-2026-45936, CVE-2026-45938, CVE-2026-45941, CVE-2026-45942,\nCVE-2026-45943, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45956, CVE-2026-45957, CVE-2026-45958,\nCVE-2026-45960, CVE-2026-45962, CVE-2026-45964, CVE-2026-45965,\nCVE-2026-45968, CVE-2026-45969, CVE-2026-45970, CVE-2026-45972,\nCVE-2026-45973, CVE-2026-45974, CVE-2026-45976, CVE-2026-45978,\nCVE-2026-45981, CVE-2026-45982, CVE-2026-45983, CVE-2026-45984,\nCVE-2026-45985, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46043,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46115, CVE-2026-46116, CVE-2026-46117,\nCVE-2026-46119, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122,\nCVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126,\nCVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46131,\nCVE-2026-46132, CVE-2026-46133, CVE-2026-46135, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46185, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46195, CVE-2026-46196,\nCVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200,\nCVE-2026-46201, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206,\nCVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46211,\nCVE-2026-46212, CVE-2026-46214, CVE-2026-46218, CVE-2026-46219,\nCVE-2026-46220, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227,\nCVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232,\nCVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236,\nCVE-2026-46238, CVE-2026-46241, CVE-2026-46243, CVE-2026-46244,\nCVE-2026-46246, CVE-2026-46247, CVE-2026-46249, CVE-2026-46250,\nCVE-2026-46251, CVE-2026-46253, CVE-2026-46254, CVE-2026-46255,\nCVE-2026-46259, CVE-2026-46260, CVE-2026-46261, CVE-2026-46265,\nCVE-2026-46266, CVE-2026-46267, CVE-2026-46270, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46289, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-46328, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:17:16Z","modified":"2026-11-07T01:46:10.910402805Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8607-1","title":"linux-azure-fde vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - 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  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:20:29Z","modified":"2026-11-07T01:46:01.058375657Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8608-1","title":"linux-azure-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:23:19Z","modified":"2026-11-09T12:47:05.283755841Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8609-1","title":"linux-azure-fde-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - 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  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:26:03Z","modified":"2026-11-07T01:45:29.525006235Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8619-1","title":"linux-hwe-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - 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  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43362, CVE-2026-43363, CVE-2026-43365,\nCVE-2026-43366, CVE-2026-43368, CVE-2026-43370, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43378, CVE-2026-43380,\nCVE-2026-43381, CVE-2026-43382, CVE-2026-43383, CVE-2026-43384,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43406, CVE-2026-43407, CVE-2026-43408,\nCVE-2026-43409, CVE-2026-43411, CVE-2026-43412, CVE-2026-43413,\nCVE-2026-43414, CVE-2026-43415, CVE-2026-43419, CVE-2026-43420,\nCVE-2026-43421, CVE-2026-43424, CVE-2026-43425, CVE-2026-43426,\nCVE-2026-43427, CVE-2026-43428, CVE-2026-43429, CVE-2026-43430,\nCVE-2026-43432, CVE-2026-43436, CVE-2026-43437, CVE-2026-43439,\nCVE-2026-43441, CVE-2026-43445, CVE-2026-43448, CVE-2026-43449,\nCVE-2026-43450, CVE-2026-43451, CVE-2026-43452, CVE-2026-43453,\nCVE-2026-43455, CVE-2026-43456, CVE-2026-43457, CVE-2026-43458,\nCVE-2026-43459, CVE-2026-43466, CVE-2026-43467, CVE-2026-43468,\nCVE-2026-43469, CVE-2026-43471, CVE-2026-43472, CVE-2026-43473,\nCVE-2026-43475, CVE-2026-43476, CVE-2026-43480, CVE-2026-43483,\nCVE-2026-43484, CVE-2026-43488, CVE-2026-43490, CVE-2026-43491,\nCVE-2026-43492, CVE-2026-43493, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43501, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45847, CVE-2026-45848, CVE-2026-45849, CVE-2026-45851,\nCVE-2026-45852, CVE-2026-45855, CVE-2026-45856, CVE-2026-45857,\nCVE-2026-45858, CVE-2026-45859, CVE-2026-45860, CVE-2026-45861,\nCVE-2026-45862, CVE-2026-45864, CVE-2026-45865, CVE-2026-45866,\nCVE-2026-45867, CVE-2026-45868, CVE-2026-45869, CVE-2026-45870,\nCVE-2026-45871, CVE-2026-45872, CVE-2026-45873, CVE-2026-45875,\nCVE-2026-45877, CVE-2026-45878, CVE-2026-45879, CVE-2026-45880,\nCVE-2026-45881, CVE-2026-45882, CVE-2026-45883, CVE-2026-45884,\nCVE-2026-45885, CVE-2026-45886, CVE-2026-45890, CVE-2026-45891,\nCVE-2026-45893, CVE-2026-45895, CVE-2026-45899, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45911,\nCVE-2026-45912, CVE-2026-45913, CVE-2026-45914, CVE-2026-45915,\nCVE-2026-45916, CVE-2026-45917, CVE-2026-45919, CVE-2026-45920,\nCVE-2026-45921, CVE-2026-45923, CVE-2026-45924, CVE-2026-45928,\nCVE-2026-45935, CVE-2026-45936, CVE-2026-45938, CVE-2026-45941,\nCVE-2026-45942, CVE-2026-45943, CVE-2026-45946, CVE-2026-45947,\nCVE-2026-45948, CVE-2026-45954, CVE-2026-45956, CVE-2026-45957,\nCVE-2026-45958, CVE-2026-45960, CVE-2026-45962, CVE-2026-45964,\nCVE-2026-45965, CVE-2026-45968, CVE-2026-45969, CVE-2026-45970,\nCVE-2026-45972, CVE-2026-45973, CVE-2026-45974, CVE-2026-45976,\nCVE-2026-45978, CVE-2026-45981, CVE-2026-45982, CVE-2026-45983,\nCVE-2026-45984, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45988, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46043, CVE-2026-46044, CVE-2026-46046, CVE-2026-46047,\nCVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052,\nCVE-2026-46053, CVE-2026-46056, CVE-2026-46058, CVE-2026-46061,\nCVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065,\nCVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46072,\nCVE-2026-46073, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077,\nCVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46082,\nCVE-2026-46083, CVE-2026-46084, CVE-2026-46086, CVE-2026-46088,\nCVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092,\nCVE-2026-46094, CVE-2026-46098, CVE-2026-46099, CVE-2026-46101,\nCVE-2026-46102, CVE-2026-46103, CVE-2026-46106, CVE-2026-46107,\nCVE-2026-46108, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112,\nCVE-2026-46113, CVE-2026-46114, CVE-2026-46115, CVE-2026-46116,\nCVE-2026-46117, CVE-2026-46119, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46135,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46185,\nCVE-2026-46186, CVE-2026-46187, CVE-2026-46189, CVE-2026-46190,\nCVE-2026-46191, CVE-2026-46193, CVE-2026-46194, CVE-2026-46195,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46243,\nCVE-2026-46244, CVE-2026-46246, CVE-2026-46247, CVE-2026-46249,\nCVE-2026-46250, CVE-2026-46251, CVE-2026-46253, CVE-2026-46254,\nCVE-2026-46255, CVE-2026-46259, CVE-2026-46260, CVE-2026-46261,\nCVE-2026-46265, CVE-2026-46266, CVE-2026-46267, CVE-2026-46270,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46289,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-46328, CVE-2026-52911,\nCVE-2026-52920, CVE-2026-52925, CVE-2026-52933, CVE-2026-52936,\nCVE-2026-52951, CVE-2026-52954, CVE-2026-52955, CVE-2026-52957,\nCVE-2026-52958, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963,\nCVE-2026-52964, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969,\nCVE-2026-52970, CVE-2026-52974, CVE-2026-52975, CVE-2026-52977,\nCVE-2026-52981, CVE-2026-52982, CVE-2026-52984, CVE-2026-52985,\nCVE-2026-52986, CVE-2026-52989, CVE-2026-52990, CVE-2026-52992,\nCVE-2026-52993, CVE-2026-52995, CVE-2026-52998, CVE-2026-52999,\nCVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004,\nCVE-2026-53006, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013,\nCVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53021,\nCVE-2026-53022, CVE-2026-53023, CVE-2026-53032, CVE-2026-53033,\nCVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037,\nCVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53043,\nCVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048,\nCVE-2026-53049, CVE-2026-53050, CVE-2026-53052, CVE-2026-53056,\nCVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061,\nCVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065,\nCVE-2026-53066, CVE-2026-53068, CVE-2026-53069, CVE-2026-53071,\nCVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075,\nCVE-2026-53076, CVE-2026-53077, CVE-2026-53082, CVE-2026-53083,\nCVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53088,\nCVE-2026-53093, CVE-2026-53094, CVE-2026-53096, CVE-2026-53097,\nCVE-2026-53098, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112,\nCVE-2026-53115, CVE-2026-53117, CVE-2026-53122, CVE-2026-53123,\nCVE-2026-53126, CVE-2026-53128, CVE-2026-53130, CVE-2026-53279,\nCVE-2026-53287, CVE-2026-53289, CVE-2026-53291, CVE-2026-53293,\nCVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53303,\nCVE-2026-53304, CVE-2026-53306, CVE-2026-53309, CVE-2026-53314,\nCVE-2026-53320, CVE-2026-53369, CVE-2026-53374, CVE-2026-53375,\nCVE-2026-53376, CVE-2026-53379, CVE-2026-63838, CVE-2026-63843,\nCVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847,\nCVE-2026-63848, CVE-2026-63851, CVE-2026-63852, CVE-2026-63854,\nCVE-2026-63855, CVE-2026-63856, CVE-2026-63860, CVE-2026-63861,\nCVE-2026-63862, CVE-2026-63865)\n","status":"published","published":"2026-07-28T07:28:45Z","modified":"2026-11-07T01:45:56.683802514Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8665-1","title":"linux-raspi, linux-raspi-realtime vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - 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  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-52911, CVE-2026-52920, CVE-2026-52925, CVE-2026-52933,\nCVE-2026-52936, CVE-2026-52951, CVE-2026-52954, CVE-2026-52955,\nCVE-2026-52957, CVE-2026-52958, CVE-2026-52961, CVE-2026-52962,\nCVE-2026-52963, CVE-2026-52964, CVE-2026-52967, CVE-2026-52968,\nCVE-2026-52969, CVE-2026-52970, CVE-2026-52974, CVE-2026-52975,\nCVE-2026-52977, CVE-2026-52981, CVE-2026-52982, CVE-2026-52984,\nCVE-2026-52985, CVE-2026-52986, CVE-2026-52989, CVE-2026-52990,\nCVE-2026-52992, CVE-2026-52993, CVE-2026-52995, CVE-2026-52998,\nCVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003,\nCVE-2026-53004, CVE-2026-53006, CVE-2026-53011, CVE-2026-53012,\nCVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016,\nCVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53032,\nCVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036,\nCVE-2026-53037, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041,\nCVE-2026-53043, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047,\nCVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53052,\nCVE-2026-53056, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060,\nCVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064,\nCVE-2026-53065, CVE-2026-53066, CVE-2026-53068, CVE-2026-53069,\nCVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074,\nCVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53082,\nCVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086,\nCVE-2026-53088, CVE-2026-53093, CVE-2026-53094, CVE-2026-53096,\nCVE-2026-53097, CVE-2026-53098, CVE-2026-53110, CVE-2026-53111,\nCVE-2026-53112, CVE-2026-53115, CVE-2026-53117, CVE-2026-53122,\nCVE-2026-53123, CVE-2026-53126, CVE-2026-53128, CVE-2026-53130,\nCVE-2026-53279, CVE-2026-53287, CVE-2026-53289, CVE-2026-53291,\nCVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296,\nCVE-2026-53303, CVE-2026-53304, CVE-2026-53306, CVE-2026-53309,\nCVE-2026-53314, CVE-2026-53320, CVE-2026-53369, CVE-2026-53374,\nCVE-2026-53375, CVE-2026-53376, CVE-2026-53379, CVE-2026-63838,\nCVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846,\nCVE-2026-63847, CVE-2026-63848, CVE-2026-63851, CVE-2026-63852,\nCVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63860,\nCVE-2026-63861, CVE-2026-63862, CVE-2026-63865, CVE-2026-64164,\nCVE-2026-64587)\n","status":"published","published":"2026-08-20T23:31:14Z","modified":"2026-11-09T12:48:40.63232576Z","updated_at":"2026-11-07T01:56:47.245871Z"}]}}