{"id":"CVE-2026-74715","aliases":["AZL-97341","BELL-CVE-2026-74715","DEBIAN-CVE-2026-74715","EUVD-2026-64402","GHSA-8qqv-vcf6-q7hx","OESA-2026-3707","OESA-2026-3987","SUSE-SU-2026:24386-1","SUSE-SU-2026:24422-1","SUSE-SU-2026:24437-1","SUSE-SU-2026:24446-1","SUSE-SU-2026:24550-1","SUSE-SU-2026:5091-1","UBUNTU-CVE-2026-74715","USN-8886-1","USN-8959-1","USN-8960-1","openSUSE-SU-2026:22167-1"],"status":"published","title":"bpf: Fix netns reference imbalance in conntrack kfuncs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00129,"percentile":0.0259,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-08-22T15:33:10Z","modified":"2026-11-10T02:51:40Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.161.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.191-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.115-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.58-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.191","6.6.160","6.12.114","6.18.57","7.1.9"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.115-2"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["7.1.9-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-7.0","fixed_in":["7.0.0-42.42~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1036.39"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-7.0","fixed_in":["7.0.0-42.42.1~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux","fixed_in":["7.0.0-42.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-aws","fixed_in":["7.0.0-1016.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-gcp","fixed_in":["7.0.0-1016.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-ibm","fixed_in":["7.0.0-1017.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-oem-7.0","fixed_in":["7.0.0-1017.17"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-oracle","fixed_in":["7.0.0-1015.16"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"linux-riscv","fixed_in":["7.0.0-42.42.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.161.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.189-r0"},{"fixed":"6.1.191-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.112-r0"},{"fixed":"6.12.115-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.18.55-r0"},{"fixed":"6.18.58-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.191"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.160"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.114"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.57"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.9"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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.170-1","6.1.170-2","6.1.170-3","6.1.172-1","6.1.174-1","6.1.176-1","6.1.177-1","6.1.180-1","6.1.187-1","6.1.190-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","6.10-1~exp1","6.10.1-1~exp1","6.10.11-1","6.10.11-1~bpo12+1","6.10.12-1","6.10.3-1","6.10.4-1","6.10.6-1","6.10.6-1~bpo12+1","6.10.7-1","6.10.9-1","6.11-1~exp1","6.11.10-1","6.11.10-1~bpo12+1","6.11.2-1","6.11.4-1","6.11.5-1","6.11.5-1~bpo12+1","6.11.6-1","6.11.7-1","6.11.9-1","6.11~rc4-1~exp1","6.11~rc5-1~exp1","6.12.10-1","6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.11-1","6.12.11-1+alpha","6.12.11-1+alpha.1","6.12.111-1","6.12.113-1","6.12.115-1","6.12.115-2","6.12.12-1","6.12.12-1~bpo12+1","6.12.13-1","6.12.15-1","6.12.16-1","6.12.17-1","6.12.19-1","6.12.20-1","6.12.21-1","6.12.22-1","6.12.22-1~bpo12+1","6.12.25-1","6.12.27-1","6.12.27-1~bpo12+1","6.12.29-1","6.12.3-1","6.12.30-1","6.12.30-1~bpo12+1","6.12.31-1","6.12.32-1","6.12.32-1~bpo12+1","6.12.33-1","6.12.33-1~bpo12+1","6.12.35-1","6.12.35-1~bpo12+1","6.12.37-1","6.12.38-1","6.12.38-1~bpo12+1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.5-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.6-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.8-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.9-1","6.12.9-1+alpha","6.12.9-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.12~rc6-1~exp1","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.10-1","6.19.10-1~bpo13+1","6.19.11-1","6.19.11-1~bpo13+1","6.19.12-1","6.19.13-1","6.19.13-1~bpo13+1","6.19.14-1","6.19.14-1~bpo13+1","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","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","6.3.1-1~exp1","6.3.11-1","6.3.2-1~exp1","6.3.4-1~exp1","6.3.5-1~exp1","6.3.7-1","6.3.7-1~bpo12+1","6.4.1-1~exp1","6.4.11-1","6.4.13-1","6.4.4-1","6.4.4-1~bpo12+1","6.4.4-2","6.4.4-3","6.4.4-3~bpo12+1","6.4~rc6-1~exp1","6.4~rc7-1~exp1","6.5.1-1~exp1","6.5.10-1","6.5.10-1~bpo12+1","6.5.13-1","6.5.3-1","6.5.3-1~bpo12+1","6.5.6-1","6.5.8-1","6.5~rc4-1~exp1","6.5~rc6-1~exp1","6.5~rc7-1~exp1","6.6.11-1","6.6.13-1","6.6.13-1~bpo12+1","6.6.15-1","6.6.15-2","6.6.3-1~exp1","6.6.4-1~exp1","6.6.7-1~exp1","6.6.8-1","6.6.9-1","6.7-1~exp1","6.7.1-1~exp1","6.7.12-1","6.7.12-1~bpo12+1","6.7.4-1~exp1","6.7.7-1","6.7.9-1","6.7.9-2","6.8.11-1","6.8.12-1","6.8.12-1~bpo12+1","6.8.9-1","6.9.10-1","6.9.10-1~bpo12+1","6.9.11-1","6.9.12-1","6.9.2-1~exp1","6.9.7-1","6.9.7-1~bpo12+1","6.9.8-1","6.9.9-1","7.0-1~exp1","7.0.1-1~exp1","7.0.10-1","7.0.10-1~bpo13+1","7.0.12-1","7.0.12-2","7.0.12-2~bpo13+1","7.0.13-1","7.0.13-1~bpo13+1","7.0.14-1","7.0.3-1","7.0.4-1","7.0.4-1~bpo13+1","7.0.7-1","7.0.7-1~bpo13+1","7.0.9-1","7.0.9-1~bpo13+1","7.1.1-1~exp1","7.1.10-1","7.1.12-1","7.1.13-1","7.1.13-1~bpo13+1","7.1.2-1~exp1","7.1.3-1","7.1.3-1+sunvdc","7.1.3-1~bpo13+1","7.1.4-1","7.1.5-1","7.1.6-1","7.1.7-1","7.1.7-1~bpo13+1","7.1.8-1","7.1.8-1~bpo13+1","7.1.8-2","7.1.9-1","7.1.9-1+sparc64","7.1~rc2-1~exp1","7.1~rc3-1~exp1","7.1~rc4-1~exp1","7.1~rc4-1~exp2","7.1~rc5-1~exp1","7.1~rc7-1~exp1","7.2.10-1","7.2.11-1","7.2.11-1~bpo13+1","7.2.12-1","7.2.13-1","7.2.14-1","7.2.15-1","7.2.2-1~exp1","7.2.3-1~exp1","7.2.6-1","7.2.6-1~bpo13+1","7.2.7-1","7.2.8-1","7.2.9-1","7.2.9-1~bpo13+1","7.2~rc3-1~exp1","7.2~rc5-1~exp1","7.2~rc7-1~exp1","7.3.1-1~exp1","7.3~rc6-1~exp1","7.3~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.115-2"}]}],"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.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"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.9-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.10-1","6.19.10-1~bpo13+1","6.19.11-1","6.19.11-1~bpo13+1","6.19.12-1","6.19.13-1","6.19.13-1~bpo13+1","6.19.14-1","6.19.14-1~bpo13+1","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","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","7.0-1~exp1","7.0.1-1~exp1","7.0.10-1","7.0.10-1~bpo13+1","7.0.12-1","7.0.12-2","7.0.12-2~bpo13+1","7.0.13-1","7.0.13-1~bpo13+1","7.0.14-1","7.0.3-1","7.0.4-1","7.0.4-1~bpo13+1","7.0.7-1","7.0.7-1~bpo13+1","7.0.9-1","7.0.9-1~bpo13+1","7.1.1-1~exp1","7.1.2-1~exp1","7.1.3-1","7.1.3-1+sunvdc","7.1.3-1~bpo13+1","7.1.4-1","7.1.5-1","7.1.6-1","7.1.7-1","7.1.7-1~bpo13+1","7.1.8-1","7.1.8-1~bpo13+1","7.1.8-2","7.1~rc2-1~exp1","7.1~rc3-1~exp1","7.1~rc4-1~exp1","7.1~rc4-1~exp2","7.1~rc5-1~exp1","7.1~rc7-1~exp1"]},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.1.25.162.oe2403sp1"}]}],"bundled":111},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.3.31.162.oe2403sp3"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1.160000.2.29"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1.160000.2.29"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1.160000.2.29"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1.159998.21.42"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1.150700.17.51.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_24","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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.90.1"}]}],"bundled":1077},{"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"}]}],"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","6.8.0-1061.64~22.04.1","6.8.0-1062.65~22.04.2","6.8.0-1063.66~22.04.1","6.8.0-1064.67~22.04.1","6.8.0-1065.68~22.04.1","6.8.0-1066.69~22.04.1","6.8.0-1069.74~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"}]}],"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","6.8.0-1063.71~22.04.1","6.8.0-1064.72~22.04.1","6.8.0-1065.73~22.04.1","6.8.0-1067.75~22.04.1","6.8.0-1068.76~22.04.1","6.8.0-1070.78~22.04.1","6.8.0-1073.82~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"}]}],"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","6.8.0-1062.69~22.04.1","6.8.0-1063.70~22.04.1","6.8.0-1064.71~22.04.1","6.8.0-1065.72~22.04.1","6.8.0-1066.73~22.04.1","6.8.0-1068.75~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"}]}],"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","6.8.0-1064.72~22.04.1","6.8.0-1065.73~22.04.1","6.8.0-1066.74~22.04.1","6.8.0-1067.75~22.04.1","6.8.0-1069.77~22.04.1","6.8.0-1070.78~22.04.1","6.8.0-1073.81~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"}]}],"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","6.8.0-136.136~22.04.1","6.8.0-138.138~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1061.62~22.04.1","6.8.0-1062.63~22.04.1","6.8.0-1063.64~22.04.1","6.8.0-1066.67~22.04.1","6.8.0-1069.70~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"}]}],"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","6.8.0-136.136.2~22.04.1","6.8.0-137.137.1~22.04.1","6.8.0-138.138.1~22.04.1","6.8.0-139.139.1~22.04.1","6.8.0-142.142.1~22.04.1","6.8.0-146.146.1~22.04.1","6.8.0-149.149.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"}]}],"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","6.8.0-1059.62~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1061.64~22.04.1","6.8.0-1062.65~22.04.1","6.8.0-1063.66~22.04.1","6.8.0-1064.67~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"}]}],"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","6.8.0-1058.61~22.04.1","6.8.0-1059.62~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1061.64~22.04.1","6.8.0-1062.65~22.04.1","6.8.0-1067.71~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"}]}],"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","6.8.0-136.136~22.04.3","6.8.0-137.137~22.04.1","6.8.0-138.138~22.04.1","6.8.0-139.139~22.04.1","6.8.0-142.142~22.04.1","6.8.0-146.146~22.04.1","6.8.0-149.149~22.04.2"]},{"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"}]}],"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","6.8.1-1056.57~22.04.2","6.8.1-1057.58~22.04.1","6.8.1-1058.59~22.04.1","6.8.1-1059.60~22.04.1","6.8.1-1060.61~22.04.1","6.8.1-1061.62~22.04.1","6.8.1-1064.65~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-136.136","6.8.0-137.137","6.8.0-138.138","6.8.0-139.139","6.8.0-142.142","6.8.0-146.146","6.8.0-147.147","6.8.0-149.149"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1061.64","6.8.0-1062.65","6.8.0-1063.66","6.8.0-1064.67","6.8.0-1065.68","6.8.0-1066.69","6.8.0-1067.70","6.8.0-1069.74"]},{"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-aws-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1007.7~24.04.2","7.0.0-1009.9~24.04.1","7.0.0-1010.10~24.04.1","7.0.0-1011.11~24.04.1","7.0.0-1012.12~24.04.1","7.0.0-1013.13~24.04.1","7.0.0-1014.14~24.04.1","7.0.0-1017.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1063.71","6.8.0-1064.72","6.8.0-1065.73","6.8.0-1067.75","6.8.0-1068.76","6.8.0-1070.78","6.8.0-1071.79"]},{"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-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1008.8~24.04.2","7.0.0-1014.14~24.04.1","7.0.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1062.69","6.8.0-1063.70","6.8.0-1064.71","6.8.0-1065.72","6.8.0-1066.73","6.8.0-1068.75","6.8.0-1069.76"]},{"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-fde-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5~24.04.1","6.17.0-1010.10~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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1007.7~24.04.3","7.0.0-1013.13~24.04.1","7.0.0-1016.16~24.04.1","7.0.0-1019.19~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"}]}],"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","6.8.0-1064.72","6.8.0-1065.73","6.8.0-1066.74","6.8.0-1067.75","6.8.0-1069.77","6.8.0-1070.78","6.8.0-1071.79","6.8.0-1073.81"]},{"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-gcp-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6~24.04.2","7.0.0-1011.11~24.04.1","7.0.0-1013.13~24.04.1","7.0.0-1014.14~24.04.1","7.0.0-1017.19~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1059.67","6.8.0-1060.68","6.8.0-1061.69","6.8.0-1062.70","6.8.0-1064.72","6.8.0-1065.73","6.8.0-1066.74","6.8.0-1068.77"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1046.50","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1049.53","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57"]},{"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-hwe-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42~24.04.1"}]}],"versions":["7.0.0-14.14~24.04.3","7.0.0-28.28~24.04.1","7.0.0-29.29~24.04.2","7.0.0-30.30~24.04.1","7.0.0-31.31~24.04.1","7.0.0-34.34~24.04.1","7.0.0-38.38~24.04.4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1061.62","6.8.0-1062.63","6.8.0-1063.64","6.8.0-1064.65","6.8.0-1065.66","6.8.0-1066.67","6.8.0-1067.68","6.8.0-1069.70"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-136.136.2","6.8.0-137.137.1","6.8.0-138.138.1","6.8.0-139.139.1","6.8.0-142.142.1","6.8.0-146.146.1","6.8.0-147.147.1","6.8.0-149.149.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"}]}],"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","6.8.0-1059.62","6.8.0-1060.63","6.8.0-1061.64","6.8.0-1062.65","6.8.0-1063.66","6.8.0-1064.67","6.8.0-1067.70"]},{"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-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1013.13~24.04.1","7.0.0-1015.15~24.04.1","7.0.0-1016.16~24.04.1","7.0.0-1018.18~24.04.1","7.0.0-1019.19~24.04.2","7.0.0-1024.25~24.04.1","7.0.0-1025.26~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1059.62.1","6.8.0-1060.63.1","6.8.0-1061.64.1","6.8.0-1062.65.1","6.8.0-1063.66.1","6.8.0-1064.67.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.39"}]}],"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","6.8.0-1030.31","6.8.0-1031.32","6.8.0-1032.34","6.8.0-1035.38"]},{"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"}]}],"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","6.8.0-1058.61","6.8.0-1059.62","6.8.0-1060.63","6.8.0-1061.64","6.8.0-1062.65","6.8.0-1063.66","6.8.0-1064.67","6.8.0-1067.71"]},{"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-oracle-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6~24.04.3","7.0.0-1011.11~24.04.1","7.0.0-1012.12~24.04.1","7.0.0-1013.13~24.04.1","7.0.0-1016.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1061.65","6.8.0-1062.66","6.8.0-1063.67","6.8.0-1064.68","6.8.0-1065.69","6.8.0-1068.72"]},{"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-riscv-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42.1~24.04.1"}]}],"versions":["7.0.0-27.27.1~24.04.2","7.0.0-28.28.1~24.04.3","7.0.0-30.30.1~24.04.1","7.0.0-31.31.1~24.04.1","7.0.0-34.34.1~24.04.1","7.0.0-38.38.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1005.5","6.8.0-1008.8","6.8.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1033.34","6.8.0-1034.35","6.8.0-1035.36","6.8.0-1036.37"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1032.37","6.8.0-1033.38","6.8.0-1036.41"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-2050.52","6.8.0-2051.53","6.8.0-2052.54","6.8.0-2053.55","6.8.0-2054.56","6.8.0-2056.58"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.1-1056.57","6.8.1-1057.58","6.8.1-1058.59","6.8.1-1059.60","6.8.1-1060.61","6.8.1-1061.62","6.8.1-1062.63","6.8.1-1064.65"]},{"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"}]}],"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","6.8.0-1061.64+fips1","6.8.0-1062.65+fips1","6.8.0-1063.66+fips1","6.8.0-1064.67+fips1","6.8.0-1065.68+fips1","6.8.0-1066.69+fips1","6.8.0-1067.70+fips1","6.8.0-1069.74+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1063.71+fips2","6.8.0-1064.72+fips1","6.8.0-1065.73+fips1","6.8.0-1067.75+fips1","6.8.0-1068.76+fips1","6.8.0-1069.77+fips1","6.8.0-1071.79+fips1","6.8.0-1073.82+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-136.136+fips2","6.8.0-137.137+fips1","6.8.0-138.138+fips1","6.8.0-139.139+fips1","6.8.0-142.142+fips1","6.8.0-146.146+fips1","6.8.0-147.147+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.8.0-1064.72+fips1","6.8.0-1065.73+fips1","6.8.0-1066.74+fips1","6.8.0-1067.75+fips1","6.8.0-1068.76+fips1","6.8.0-1070.78+fips1","6.8.0-1071.79+fips1","6.8.0-1073.81+fips1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42"}]}],"versions":["6.17.0-5.5","6.17.0-6.6","6.17.0-8.8","6.18.0-8.8","6.18.0-9.9","6.19.0-3.3","6.19.0-5.5","6.19.0-6.6","6.19.0-9.9","7.0.0-7.7","7.0.0-10.10","7.0.0-12.12","7.0.0-13.13","7.0.0-14.14","7.0.0-15.15","7.0.0-22.22","7.0.0-27.27","7.0.0-28.28","7.0.0-29.29","7.0.0-30.30","7.0.0-31.31","7.0.0-34.34","7.0.0-38.38"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1016.17"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1002.2","6.19.0-1003.3","7.0.0-1001.1","7.0.0-1003.3","7.0.0-1004.4","7.0.0-1006.6","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13","7.0.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.19.0-1001.1","6.19.0-1002.2","7.0.0-1001.1","7.0.0-1002.2","7.0.0-1003.3","7.0.0-1004.4","7.0.0-1007.7","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1014.14","7.0.0-1017.17","7.0.0-1019.20","7.0.0-1020.21"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1003.3","7.0.0-1004.4","7.0.0-1006.6","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1013.13","7.0.0-1016.16","7.0.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1016.18"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1001.1","7.0.0-1001.1","7.0.0-1002.2","7.0.0-1003.3","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1008.8","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1013.13","7.0.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1002.3","7.0.0-1003.4","7.0.0-1005.6","7.0.0-1006.7","7.0.0-1007.8","7.0.0-1008.9","7.0.0-1010.11"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1017.17"}]}],"versions":["6.19.0-1002.2","6.19.0-1003.3","7.0.0-1002.2","7.0.0-1004.4","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13","7.0.0-1014.14","7.0.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1005.5","7.0.0-1006.6","7.0.0-1009.9","7.0.0-1013.13","7.0.0-1015.15","7.0.0-1016.16","7.0.0-1018.18","7.0.0-1025.26"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-nvidia-bos","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-2012.12","7.0.0-2015.15","7.0.0-2016.16","7.0.0-2018.18","7.0.0-2022.23","7.0.0-2024.25"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-oem-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1017.17"}]}],"versions":["7.0.0-1005.5","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1013.13","7.0.0-1014.14","7.0.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1015.16"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1001.1","6.19.0-1002.2","7.0.0-1001.1","7.0.0-1002.2","7.0.0-1003.3","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","7.0.0-1004.4","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1014.14","7.0.0-1015.15","7.0.0-1016.16","7.0.0-1017.17","7.0.0-1019.19","7.0.0-1020.20","7.0.0-1023.23"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1001.2","7.0.0-10.10.3","7.0.0-12.12.1","7.0.0-14.14.1","7.0.0-22.22.1","7.0.0-27.27.1","7.0.0-28.28.1","7.0.0-29.29.1","7.0.0-30.30.1","7.0.0-31.31.1","7.0.0-34.34.1","7.0.0-38.38.1","7.0.0-43.43.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42.1"}]}],"versions":["6.17.0-5.5.1","7.0.0-7.7.1","7.0.0-12.12.1","7.0.0-14.14.2","7.0.0-22.22.1","7.0.0-27.27.1","7.0.0-28.28.1","7.0.0-29.29.1","7.0.0-30.30.1","7.0.0-31.31.1","7.0.0-34.34.1","7.0.0-38.38.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1036.39"}]}],"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","6.8.0-1030.31","6.8.0-1031.32","6.8.0-1032.34","6.8.0-1035.38"],"bundled":684},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42~24.04.1"}]}],"versions":["7.0.0-14.14~24.04.3","7.0.0-28.28~24.04.1","7.0.0-29.29~24.04.2","7.0.0-30.30~24.04.1","7.0.0-31.31~24.04.1","7.0.0-34.34~24.04.1","7.0.0-38.38~24.04.4"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-42.42"}]}],"versions":["6.17.0-5.5","6.17.0-6.6","6.17.0-8.8","6.18.0-8.8","6.18.0-9.9","6.19.0-3.3","6.19.0-5.5","6.19.0-6.6","6.19.0-9.9","7.0.0-7.7","7.0.0-10.10","7.0.0-12.12","7.0.0-13.13","7.0.0-14.14","7.0.0-15.15","7.0.0-22.22","7.0.0-27.27","7.0.0-28.28","7.0.0-29.29","7.0.0-30.30","7.0.0-31.31","7.0.0-34.34","7.0.0-38.38"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1016.17"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1002.2","6.19.0-1003.3","7.0.0-1001.1","7.0.0-1003.3","7.0.0-1004.4","7.0.0-1006.6","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13","7.0.0-1014.14"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1016.18"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1001.1","7.0.0-1001.1","7.0.0-1002.2","7.0.0-1003.3","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1008.8","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1013.13","7.0.0-1014.14"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1017.17"}]}],"versions":["6.19.0-1002.2","6.19.0-1003.3","7.0.0-1002.2","7.0.0-1004.4","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13","7.0.0-1014.14","7.0.0-1015.15"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1015.16"}]}],"versions":["6.17.0-1002.2","6.17.0-1003.3","6.19.0-1001.1","6.19.0-1002.2","7.0.0-1001.1","7.0.0-1002.2","7.0.0-1003.3","7.0.0-1005.5","7.0.0-1007.7","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1012.12","7.0.0-1013.13"],"bundled":2894},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-oem-7.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-1017.17"}]}],"versions":["7.0.0-1005.5","7.0.0-1008.8","7.0.0-1009.9","7.0.0-1010.10","7.0.0-1011.11","7.0.0-1013.13","7.0.0-1014.14","7.0.0-1015.15"],"bundled":2889},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1.160000.2.29"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.40.1"}]}],"bundled":129}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/cfde990193135a35637e55f69e83e4ab441e60ab","tags":["web"]},{"url":"https://git.kernel.org/stable/c/fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8","tags":["web"]},{"url":"https://git.kernel.org/stable/c/41731d4290400cb898f15f049ae4018d45415e69","tags":["web"]},{"url":"https://git.kernel.org/stable/c/4af94462c0ca2187a02a1a6641020ae888c74d5c","tags":["web"]},{"url":"https://git.kernel.org/stable/c/e5e060eb63d10b41ab60fd955649479d99b38210","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/fdeba03fea78407a8c52faa99177c9f7f29f90eb","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74715","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-8qqv-vcf6-q7hx"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-74715","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74715.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-74715","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46325","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64523","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68471","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72405","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72420","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74317","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74509","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74514","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74520","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74536","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74606","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74608","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74614","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74620","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74624","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74636","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74696","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74747","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80536","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80549","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80558","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80560","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80647","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80725","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68095","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624386-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1234634","tags":["report"]},{"url":"https://bugzilla.suse.com/1264042","tags":["report"]},{"url":"https://bugzilla.suse.com/1267430","tags":["report"]},{"url":"https://bugzilla.suse.com/1268315","tags":["report"]},{"url":"https://bugzilla.suse.com/1269561","tags":["report"]},{"url":"https://bugzilla.suse.com/1272178","tags":["report"]},{"url":"https://bugzilla.suse.com/1272509","tags":["report"]},{"url":"https://bugzilla.suse.com/1272898","tags":["report"]},{"url":"https://bugzilla.suse.com/1272901","tags":["report"]},{"url":"https://bugzilla.suse.com/1272952","tags":["report"]},{"url":"https://bugzilla.suse.com/1272955","tags":["report"]},{"url":"https://bugzilla.suse.com/1272956","tags":["report"]},{"url":"https://bugzilla.suse.com/1273599","tags":["report"]},{"url":"https://bugzilla.suse.com/1273751","tags":["report"]},{"url":"https://bugzilla.suse.com/1273764","tags":["report"]},{"url":"https://bugzilla.suse.com/1273865","tags":["report"]},{"url":"https://bugzilla.suse.com/1274039","tags":["report"]},{"url":"https://bugzilla.suse.com/1274080","tags":["report"]},{"url":"https://bugzilla.suse.com/1274256","tags":["report"]},{"url":"https://bugzilla.suse.com/1274653","tags":["report"]},{"url":"https://bugzilla.suse.com/1275510","tags":["report"]},{"url":"https://bugzilla.suse.com/1275564","tags":["report"]},{"url":"https://bugzilla.suse.com/1275644","tags":["report"]},{"url":"https://bugzilla.suse.com/1275785","tags":["report"]},{"url":"https://bugzilla.suse.com/1275786","tags":["report"]},{"url":"https://bugzilla.suse.com/1275964","tags":["report"]},{"url":"https://bugzilla.suse.com/1276330","tags":["report"]},{"url":"https://bugzilla.suse.com/1276791","tags":["report"]},{"url":"https://bugzilla.suse.com/1276836","tags":["report"]},{"url":"https://bugzilla.suse.com/1276873","tags":["report"]},{"url":"https://bugzilla.suse.com/1276907","tags":["report"]},{"url":"https://bugzilla.suse.com/1276951","tags":["report"]},{"url":"https://bugzilla.suse.com/1277103","tags":["report"]},{"url":"https://bugzilla.suse.com/1277174","tags":["report"]},{"url":"https://bugzilla.suse.com/1277260","tags":["report"]},{"url":"https://bugzilla.suse.com/1277338","tags":["report"]},{"url":"https://bugzilla.suse.com/1277357","tags":["report"]},{"url":"https://bugzilla.suse.com/1277599","tags":["report"]},{"url":"https://bugzilla.suse.com/1277602","tags":["report"]},{"url":"https://bugzilla.suse.com/1277603","tags":["report"]},{"url":"https://bugzilla.suse.com/1277614","tags":["report"]},{"url":"https://bugzilla.suse.com/1277663","tags":["report"]},{"url":"https://bugzilla.suse.com/1277665","tags":["report"]},{"url":"https://bugzilla.suse.com/1277691","tags":["report"]},{"url":"https://bugzilla.suse.com/1277695","tags":["report"]},{"url":"https://bugzilla.suse.com/1277747","tags":["report"]},{"url":"https://bugzilla.suse.com/1277804","tags":["report"]},{"url":"https://bugzilla.suse.com/1277821","tags":["report"]},{"url":"https://bugzilla.suse.com/1277889","tags":["report"]},{"url":"https://bugzilla.suse.com/1277890","tags":["report"]},{"url":"https://bugzilla.suse.com/1277894","tags":["report"]},{"url":"https://bugzilla.suse.com/1277931","tags":["report"]},{"url":"https://bugzilla.suse.com/1278033","tags":["report"]},{"url":"https://bugzilla.suse.com/1278232","tags":["report"]},{"url":"https://bugzilla.suse.com/1279706","tags":["report"]},{"url":"https://bugzilla.suse.com/1280229","tags":["report"]},{"url":"https://bugzilla.suse.com/1280259","tags":["report"]},{"url":"https://bugzilla.suse.com/1280496","tags":["report"]},{"url":"https://bugzilla.suse.com/1280552","tags":["report"]},{"url":"https://bugzilla.suse.com/1280743","tags":["report"]},{"url":"https://bugzilla.suse.com/1280769","tags":["report"]},{"url":"https://bugzilla.suse.com/1280770","tags":["report"]},{"url":"https://bugzilla.suse.com/1280950","tags":["report"]},{"url":"https://bugzilla.suse.com/1280966","tags":["report"]},{"url":"https://bugzilla.suse.com/1281042","tags":["report"]},{"url":"https://bugzilla.suse.com/1281144","tags":["report"]},{"url":"https://bugzilla.suse.com/1281162","tags":["report"]},{"url":"https://bugzilla.suse.com/1281280","tags":["report"]},{"url":"https://bugzilla.suse.com/1281726","tags":["report"]},{"url":"https://bugzilla.suse.com/1281771","tags":["report"]},{"url":"https://bugzilla.suse.com/1281819","tags":["report"]},{"url":"https://bugzilla.suse.com/1282005","tags":["report"]},{"url":"https://bugzilla.suse.com/1282274","tags":["report"]},{"url":"https://bugzilla.suse.com/1282615","tags":["report"]},{"url":"https://bugzilla.suse.com/1282742","tags":["report"]},{"url":"https://bugzilla.suse.com/1282768","tags":["report"]},{"url":"https://bugzilla.suse.com/1282769","tags":["report"]},{"url":"https://bugzilla.suse.com/1282770","tags":["report"]},{"url":"https://bugzilla.suse.com/1282784","tags":["report"]},{"url":"https://bugzilla.suse.com/1282869","tags":["report"]},{"url":"https://bugzilla.suse.com/1282932","tags":["report"]},{"url":"https://bugzilla.suse.com/1283037","tags":["report"]},{"url":"https://bugzilla.suse.com/1283142","tags":["report"]},{"url":"https://bugzilla.suse.com/1283144","tags":["report"]},{"url":"https://bugzilla.suse.com/1283153","tags":["report"]},{"url":"https://bugzilla.suse.com/1283158","tags":["report"]},{"url":"https://bugzilla.suse.com/1283454","tags":["report"]},{"url":"https://bugzilla.suse.com/1283812","tags":["report"]},{"url":"https://bugzilla.suse.com/1283823","tags":["report"]},{"url":"https://bugzilla.suse.com/1283835","tags":["report"]},{"url":"https://bugzilla.suse.com/1283850","tags":["report"]},{"url":"https://bugzilla.suse.com/1283851","tags":["report"]},{"url":"https://bugzilla.suse.com/1283853","tags":["report"]},{"url":"https://bugzilla.suse.com/1283855","tags":["report"]},{"url":"https://bugzilla.suse.com/1283856","tags":["report"]},{"url":"https://bugzilla.suse.com/1283858","tags":["report"]},{"url":"https://bugzilla.suse.com/1283859","tags":["report"]},{"url":"https://bugzilla.suse.com/1283862","tags":["report"]},{"url":"https://bugzilla.suse.com/1283873","tags":["report"]},{"url":"https://bugzilla.suse.com/1283877","tags":["report"]},{"url":"https://bugzilla.suse.com/1283894","tags":["report"]},{"url":"https://bugzilla.suse.com/1283936","tags":["report"]},{"url":"https://bugzilla.suse.com/1283946","tags":["report"]},{"url":"https://bugzilla.suse.com/1283963","tags":["report"]},{"url":"https://bugzilla.suse.com/1283979","tags":["report"]},{"url":"https://bugzilla.suse.com/1284064","tags":["report"]},{"url":"https://bugzilla.suse.com/1284288","tags":["report"]},{"url":"https://bugzilla.suse.com/1284289","tags":["report"]},{"url":"https://bugzilla.suse.com/1284291","tags":["report"]},{"url":"https://bugzilla.suse.com/1284295","tags":["report"]},{"url":"https://bugzilla.suse.com/1284298","tags":["report"]},{"url":"https://bugzilla.suse.com/1284310","tags":["report"]},{"url":"https://bugzilla.suse.com/1284312","tags":["report"]},{"url":"https://bugzilla.suse.com/1284408","tags":["report"]},{"url":"https://bugzilla.suse.com/1284412","tags":["report"]},{"url":"https://bugzilla.suse.com/1284415","tags":["report"]},{"url":"https://bugzilla.suse.com/1284419","tags":["report"]},{"url":"https://bugzilla.suse.com/1284422","tags":["report"]},{"url":"https://bugzilla.suse.com/1284424","tags":["report"]},{"url":"https://bugzilla.suse.com/1284462","tags":["report"]},{"url":"https://bugzilla.suse.com/1284559","tags":["report"]},{"url":"https://bugzilla.suse.com/1284581","tags":["report"]},{"url":"https://bugzilla.suse.com/1284605","tags":["report"]},{"url":"https://bugzilla.suse.com/1284606","tags":["report"]},{"url":"https://bugzilla.suse.com/1284647","tags":["report"]},{"url":"https://bugzilla.suse.com/1284649","tags":["report"]},{"url":"https://bugzilla.suse.com/1284655","tags":["report"]},{"url":"https://bugzilla.suse.com/1284713","tags":["report"]},{"url":"https://bugzilla.suse.com/1284746","tags":["report"]},{"url":"https://bugzilla.suse.com/1284790","tags":["report"]},{"url":"https://bugzilla.suse.com/1284791","tags":["report"]},{"url":"https://bugzilla.suse.com/1285684","tags":["report"]},{"url":"https://bugzilla.suse.com/1285685","tags":["report"]},{"url":"https://bugzilla.suse.com/1285989","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74611","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99999","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624422-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624437-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624446-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624550-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1232383","tags":["report"]},{"url":"https://bugzilla.suse.com/1233187","tags":["report"]},{"url":"https://bugzilla.suse.com/1233565","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1246086","tags":["report"]},{"url":"https://bugzilla.suse.com/1248354","tags":["report"]},{"url":"https://bugzilla.suse.com/1250656","tags":["report"]},{"url":"https://bugzilla.suse.com/1255222","tags":["report"]},{"url":"https://bugzilla.suse.com/1256632","tags":["report"]},{"url":"https://bugzilla.suse.com/1257737","tags":["report"]},{"url":"https://bugzilla.suse.com/1258184","tags":["report"]},{"url":"https://bugzilla.suse.com/1264022","tags":["report"]},{"url":"https://bugzilla.suse.com/1264024","tags":["report"]},{"url":"https://bugzilla.suse.com/1264267","tags":["report"]},{"url":"https://bugzilla.suse.com/1264985","tags":["report"]},{"url":"https://bugzilla.suse.com/1267203","tags":["report"]},{"url":"https://bugzilla.suse.com/1267238","tags":["report"]},{"url":"https://bugzilla.suse.com/1267373","tags":["report"]},{"url":"https://bugzilla.suse.com/1267681","tags":["report"]},{"url":"https://bugzilla.suse.com/1267720","tags":["report"]},{"url":"https://bugzilla.suse.com/1269264","tags":["report"]},{"url":"https://bugzilla.suse.com/1269364","tags":["report"]},{"url":"https://bugzilla.suse.com/1269532","tags":["report"]},{"url":"https://bugzilla.suse.com/1269655","tags":["report"]},{"url":"https://bugzilla.suse.com/1269798","tags":["report"]},{"url":"https://bugzilla.suse.com/1271349","tags":["report"]},{"url":"https://bugzilla.suse.com/1272261","tags":["report"]},{"url":"https://bugzilla.suse.com/1272296","tags":["report"]},{"url":"https://bugzilla.suse.com/1273292","tags":["report"]},{"url":"https://bugzilla.suse.com/1273557","tags":["report"]},{"url":"https://bugzilla.suse.com/1273803","tags":["report"]},{"url":"https://bugzilla.suse.com/1273805","tags":["report"]},{"url":"https://bugzilla.suse.com/1273809","tags":["report"]},{"url":"https://bugzilla.suse.com/1273839","tags":["report"]},{"url":"https://bugzilla.suse.com/1273880","tags":["report"]},{"url":"https://bugzilla.suse.com/1273970","tags":["report"]},{"url":"https://bugzilla.suse.com/1273999","tags":["report"]},{"url":"https://bugzilla.suse.com/1274082","tags":["report"]},{"url":"https://bugzilla.suse.com/1274261","tags":["report"]},{"url":"https://bugzilla.suse.com/1274292","tags":["report"]},{"url":"https://bugzilla.suse.com/1274550","tags":["report"]},{"url":"https://bugzilla.suse.com/1274902","tags":["report"]},{"url":"https://bugzilla.suse.com/1274949","tags":["report"]},{"url":"https://bugzilla.suse.com/1275524","tags":["report"]},{"url":"https://bugzilla.suse.com/1275568","tags":["report"]},{"url":"https://bugzilla.suse.com/1275575","tags":["report"]},{"url":"https://bugzilla.suse.com/1275671","tags":["report"]},{"url":"https://bugzilla.suse.com/1275672","tags":["report"]},{"url":"https://bugzilla.suse.com/1275678","tags":["report"]},{"url":"https://bugzilla.suse.com/1275683","tags":["report"]},{"url":"https://bugzilla.suse.com/1275689","tags":["report"]},{"url":"https://bugzilla.suse.com/1275692","tags":["report"]},{"url":"https://bugzilla.suse.com/1275810","tags":["report"]},{"url":"https://bugzilla.suse.com/1275811","tags":["report"]},{"url":"https://bugzilla.suse.com/1275813","tags":["report"]},{"url":"https://bugzilla.suse.com/1275939","tags":["report"]},{"url":"https://bugzilla.suse.com/1275944","tags":["report"]},{"url":"https://bugzilla.suse.com/1275947","tags":["report"]},{"url":"https://bugzilla.suse.com/1275951","tags":["report"]},{"url":"https://bugzilla.suse.com/1275957","tags":["report"]},{"url":"https://bugzilla.suse.com/1275958","tags":["report"]},{"url":"https://bugzilla.suse.com/1275959","tags":["report"]},{"url":"https://bugzilla.suse.com/1276271","tags":["report"]},{"url":"https://bugzilla.suse.com/1276280","tags":["report"]},{"url":"https://bugzilla.suse.com/1276321","tags":["report"]},{"url":"https://bugzilla.suse.com/1276343","tags":["report"]},{"url":"https://bugzilla.suse.com/1276363","tags":["report"]},{"url":"https://bugzilla.suse.com/1276382","tags":["report"]},{"url":"https://bugzilla.suse.com/1276384","tags":["report"]},{"url":"https://bugzilla.suse.com/1276387","tags":["report"]},{"url":"https://bugzilla.suse.com/1276393","tags":["report"]},{"url":"https://bugzilla.suse.com/1276444","tags":["report"]},{"url":"https://bugzilla.suse.com/1276450","tags":["report"]},{"url":"https://bugzilla.suse.com/1276451","tags":["report"]},{"url":"https://bugzilla.suse.com/1276453","tags":["report"]},{"url":"https://bugzilla.suse.com/1276454","tags":["report"]},{"url":"https://bugzilla.suse.com/1276457","tags":["report"]},{"url":"https://bugzilla.suse.com/1276476","tags":["report"]},{"url":"https://bugzilla.suse.com/1276479","tags":["report"]},{"url":"https://bugzilla.suse.com/1276482","tags":["report"]},{"url":"https://bugzilla.suse.com/1276483","tags":["report"]},{"url":"https://bugzilla.suse.com/1276495","tags":["report"]},{"url":"https://bugzilla.suse.com/1276499","tags":["report"]},{"url":"https://bugzilla.suse.com/1276502","tags":["report"]},{"url":"https://bugzilla.suse.com/1276517","tags":["report"]},{"url":"https://bugzilla.suse.com/1276522","tags":["report"]},{"url":"https://bugzilla.suse.com/1276574","tags":["report"]},{"url":"https://bugzilla.suse.com/1276576","tags":["report"]},{"url":"https://bugzilla.suse.com/1276585","tags":["report"]},{"url":"https://bugzilla.suse.com/1276592","tags":["report"]},{"url":"https://bugzilla.suse.com/1276765","tags":["report"]},{"url":"https://bugzilla.suse.com/1276769","tags":["report"]},{"url":"https://bugzilla.suse.com/1276770","tags":["report"]},{"url":"https://bugzilla.suse.com/1276772","tags":["report"]},{"url":"https://bugzilla.suse.com/1276773","tags":["report"]},{"url":"https://bugzilla.suse.com/1276776","tags":["report"]},{"url":"https://bugzilla.suse.com/1276778","tags":["report"]},{"url":"https://bugzilla.suse.com/1276779","tags":["report"]},{"url":"https://bugzilla.suse.com/1276798","tags":["report"]},{"url":"https://bugzilla.suse.com/1276844","tags":["report"]},{"url":"https://bugzilla.suse.com/1276925","tags":["report"]},{"url":"https://bugzilla.suse.com/1276933","tags":["report"]},{"url":"https://bugzilla.suse.com/1276934","tags":["report"]},{"url":"https://bugzilla.suse.com/1276935","tags":["report"]},{"url":"https://bugzilla.suse.com/1276940","tags":["report"]},{"url":"https://bugzilla.suse.com/1276949","tags":["report"]},{"url":"https://bugzilla.suse.com/1276956","tags":["report"]},{"url":"https://bugzilla.suse.com/1277044","tags":["report"]},{"url":"https://bugzilla.suse.com/1277046","tags":["report"]},{"url":"https://bugzilla.suse.com/1277053","tags":["report"]},{"url":"https://bugzilla.suse.com/1277067","tags":["report"]},{"url":"https://bugzilla.suse.com/1277069","tags":["report"]},{"url":"https://bugzilla.suse.com/1277071","tags":["report"]},{"url":"https://bugzilla.suse.com/1277072","tags":["report"]},{"url":"https://bugzilla.suse.com/1277075","tags":["report"]},{"url":"https://bugzilla.suse.com/1277080","tags":["report"]},{"url":"https://bugzilla.suse.com/1277082","tags":["report"]},{"url":"https://bugzilla.suse.com/1277089","tags":["report"]},{"url":"https://bugzilla.suse.com/1277091","tags":["report"]},{"url":"https://bugzilla.suse.com/1277094","tags":["report"]},{"url":"https://bugzilla.suse.com/1277113","tags":["report"]},{"url":"https://bugzilla.suse.com/1277121","tags":["report"]},{"url":"https://bugzilla.suse.com/1277133","tags":["report"]},{"url":"https://bugzilla.suse.com/1277158","tags":["report"]},{"url":"https://bugzilla.suse.com/1277161","tags":["report"]},{"url":"https://bugzilla.suse.com/1277163","tags":["report"]},{"url":"https://bugzilla.suse.com/1277166","tags":["report"]},{"url":"https://bugzilla.suse.com/1277167","tags":["report"]},{"url":"https://bugzilla.suse.com/1277169","tags":["report"]},{"url":"https://bugzilla.suse.com/1277170","tags":["report"]},{"url":"https://bugzilla.suse.com/1277171","tags":["report"]},{"url":"https://bugzilla.suse.com/1277173","tags":["report"]},{"url":"https://bugzilla.suse.com/1277176","tags":["report"]},{"url":"https://bugzilla.suse.com/1277177","tags":["report"]},{"url":"https://bugzilla.suse.com/1277184","tags":["report"]},{"url":"https://bugzilla.suse.com/1277190","tags":["report"]},{"url":"https://bugzilla.suse.com/1277191","tags":["report"]},{"url":"https://bugzilla.suse.com/1277192","tags":["report"]},{"url":"https://bugzilla.suse.com/1277193","tags":["report"]},{"url":"https://bugzilla.suse.com/1277194","tags":["report"]},{"url":"https://bugzilla.suse.com/1277195","tags":["report"]},{"url":"https://bugzilla.suse.com/1277196","tags":["report"]},{"url":"https://bugzilla.suse.com/1277197","tags":["report"]},{"url":"https://bugzilla.suse.com/1277201","tags":["report"]},{"url":"https://bugzilla.suse.com/1277211","tags":["report"]},{"url":"https://bugzilla.suse.com/1277214","tags":["report"]},{"url":"https://bugzilla.suse.com/1277221","tags":["report"]},{"url":"https://bugzilla.suse.com/1277222","tags":["report"]},{"url":"https://bugzilla.suse.com/1277225","tags":["report"]},{"url":"https://bugzilla.suse.com/1277240","tags":["report"]},{"url":"https://bugzilla.suse.com/1277254","tags":["report"]},{"url":"https://bugzilla.suse.com/1277264","tags":["report"]},{"url":"https://bugzilla.suse.com/1277280","tags":["report"]},{"url":"https://bugzilla.suse.com/1277282","tags":["report"]},{"url":"https://bugzilla.suse.com/1277307","tags":["report"]},{"url":"https://bugzilla.suse.com/1277312","tags":["report"]},{"url":"https://bugzilla.suse.com/1277317","tags":["report"]},{"url":"https://bugzilla.suse.com/1277319","tags":["report"]},{"url":"https://bugzilla.suse.com/1277323","tags":["report"]},{"url":"https://bugzilla.suse.com/1277325","tags":["report"]},{"url":"https://bugzilla.suse.com/1277329","tags":["report"]},{"url":"https://bugzilla.suse.com/1277330","tags":["report"]},{"url":"https://bugzilla.suse.com/1277336","tags":["report"]},{"url":"https://bugzilla.suse.com/1277337","tags":["report"]},{"url":"https://bugzilla.suse.com/1277339","tags":["report"]},{"url":"https://bugzilla.suse.com/1277343","tags":["report"]},{"url":"https://bugzilla.suse.com/1277344","tags":["report"]},{"url":"https://bugzilla.suse.com/1277345","tags":["report"]},{"url":"https://bugzilla.suse.com/1277355","tags":["report"]},{"url":"https://bugzilla.suse.com/1277356","tags":["report"]},{"url":"https://bugzilla.suse.com/1277362","tags":["report"]},{"url":"https://bugzilla.suse.com/1277364","tags":["report"]},{"url":"https://bugzilla.suse.com/1277365","tags":["report"]},{"url":"https://bugzilla.suse.com/1277383","tags":["report"]},{"url":"https://bugzilla.suse.com/1277387","tags":["report"]},{"url":"https://bugzilla.suse.com/1277389","tags":["report"]},{"url":"https://bugzilla.suse.com/1277456","tags":["report"]},{"url":"https://bugzilla.suse.com/1277457","tags":["report"]},{"url":"https://bugzilla.suse.com/1277461","tags":["report"]},{"url":"https://bugzilla.suse.com/1277467","tags":["report"]},{"url":"https://bugzilla.suse.com/1277472","tags":["report"]},{"url":"https://bugzilla.suse.com/1277487","tags":["report"]},{"url":"https://bugzilla.suse.com/1277488","tags":["report"]},{"url":"https://bugzilla.suse.com/1277497","tags":["report"]},{"url":"https://bugzilla.suse.com/1277520","tags":["report"]},{"url":"https://bugzilla.suse.com/1277522","tags":["report"]},{"url":"https://bugzilla.suse.com/1277529","tags":["report"]},{"url":"https://bugzilla.suse.com/1277530","tags":["report"]},{"url":"https://bugzilla.suse.com/1277533","tags":["report"]},{"url":"https://bugzilla.suse.com/1277538","tags":["report"]},{"url":"https://bugzilla.suse.com/1277540","tags":["report"]},{"url":"https://bugzilla.suse.com/1277541","tags":["report"]},{"url":"https://bugzilla.suse.com/1277542","tags":["report"]},{"url":"https://bugzilla.suse.com/1277543","tags":["report"]},{"url":"https://bugzilla.suse.com/1277546","tags":["report"]},{"url":"https://bugzilla.suse.com/1277554","tags":["report"]},{"url":"https://bugzilla.suse.com/1277560","tags":["report"]},{"url":"https://bugzilla.suse.com/1277566","tags":["report"]},{"url":"https://bugzilla.suse.com/1277576","tags":["report"]},{"url":"https://bugzilla.suse.com/1277578","tags":["report"]},{"url":"https://bugzilla.suse.com/1277593","tags":["report"]},{"url":"https://bugzilla.suse.com/1277607","tags":["report"]},{"url":"https://bugzilla.suse.com/1277609","tags":["report"]},{"url":"https://bugzilla.suse.com/1277610","tags":["report"]},{"url":"https://bugzilla.suse.com/1277612","tags":["report"]},{"url":"https://bugzilla.suse.com/1277621","tags":["report"]},{"url":"https://bugzilla.suse.com/1277623","tags":["report"]},{"url":"https://bugzilla.suse.com/1277637","tags":["report"]},{"url":"https://bugzilla.suse.com/1277645","tags":["report"]},{"url":"https://bugzilla.suse.com/1277657","tags":["report"]},{"url":"https://bugzilla.suse.com/1277677","tags":["report"]},{"url":"https://bugzilla.suse.com/1277682","tags":["report"]},{"url":"https://bugzilla.suse.com/1277690","tags":["report"]},{"url":"https://bugzilla.suse.com/1277730","tags":["report"]},{"url":"https://bugzilla.suse.com/1277741","tags":["report"]},{"url":"https://bugzilla.suse.com/1277744","tags":["report"]},{"url":"https://bugzilla.suse.com/1277746","tags":["report"]},{"url":"https://bugzilla.suse.com/1277754","tags":["report"]},{"url":"https://bugzilla.suse.com/1277770","tags":["report"]},{"url":"https://bugzilla.suse.com/1277771","tags":["report"]},{"url":"https://bugzilla.suse.com/1277772","tags":["report"]},{"url":"https://bugzilla.suse.com/1277835","tags":["report"]},{"url":"https://bugzilla.suse.com/1277836","tags":["report"]},{"url":"https://bugzilla.suse.com/1277839","tags":["report"]},{"url":"https://bugzilla.suse.com/1277875","tags":["report"]},{"url":"https://bugzilla.suse.com/1277877","tags":["report"]},{"url":"https://bugzilla.suse.com/1277879","tags":["report"]},{"url":"https://bugzilla.suse.com/1277880","tags":["report"]},{"url":"https://bugzilla.suse.com/1277881","tags":["report"]},{"url":"https://bugzilla.suse.com/1277882","tags":["report"]},{"url":"https://bugzilla.suse.com/1277884","tags":["report"]},{"url":"https://bugzilla.suse.com/1277893","tags":["report"]},{"url":"https://bugzilla.suse.com/1277903","tags":["report"]},{"url":"https://bugzilla.suse.com/1277934","tags":["report"]},{"url":"https://bugzilla.suse.com/1278028","tags":["report"]},{"url":"https://bugzilla.suse.com/1278030","tags":["report"]},{"url":"https://bugzilla.suse.com/1278041","tags":["report"]},{"url":"https://bugzilla.suse.com/1278050","tags":["report"]},{"url":"https://bugzilla.suse.com/1278057","tags":["report"]},{"url":"https://bugzilla.suse.com/1278101","tags":["report"]},{"url":"https://bugzilla.suse.com/1278123","tags":["report"]},{"url":"https://bugzilla.suse.com/1278132","tags":["report"]},{"url":"https://bugzilla.suse.com/1278139","tags":["report"]},{"url":"https://bugzilla.suse.com/1278153","tags":["report"]},{"url":"https://bugzilla.suse.com/1278160","tags":["report"]},{"url":"https://bugzilla.suse.com/1278181","tags":["report"]},{"url":"https://bugzilla.suse.com/1278194","tags":["report"]},{"url":"https://bugzilla.suse.com/1278200","tags":["report"]},{"url":"https://bugzilla.suse.com/1278201","tags":["report"]},{"url":"https://bugzilla.suse.com/1278202","tags":["report"]},{"url":"https://bugzilla.suse.com/1278207","tags":["report"]},{"url":"https://bugzilla.suse.com/1278212","tags":["report"]},{"url":"https://bugzilla.suse.com/1278214","tags":["report"]},{"url":"https://bugzilla.suse.com/1278222","tags":["report"]},{"url":"https://bugzilla.suse.com/1278241","tags":["report"]},{"url":"https://bugzilla.suse.com/1278246","tags":["report"]},{"url":"https://bugzilla.suse.com/1278296","tags":["report"]},{"url":"https://bugzilla.suse.com/1278310","tags":["report"]},{"url":"https://bugzilla.suse.com/1278313","tags":["report"]},{"url":"https://bugzilla.suse.com/1278317","tags":["report"]},{"url":"https://bugzilla.suse.com/1278319","tags":["report"]},{"url":"https://bugzilla.suse.com/1278320","tags":["report"]},{"url":"https://bugzilla.suse.com/1278323","tags":["report"]},{"url":"https://bugzilla.suse.com/1278325","tags":["report"]},{"url":"https://bugzilla.suse.com/1278326","tags":["report"]},{"url":"https://bugzilla.suse.com/1278334","tags":["report"]},{"url":"https://bugzilla.suse.com/1278337","tags":["report"]},{"url":"https://bugzilla.suse.com/1278343","tags":["report"]},{"url":"https://bugzilla.suse.com/1278377","tags":["report"]},{"url":"https://bugzilla.suse.com/1278393","tags":["report"]},{"url":"https://bugzilla.suse.com/1278400","tags":["report"]},{"url":"https://bugzilla.suse.com/1278412","tags":["report"]},{"url":"https://bugzilla.suse.com/1278415","tags":["report"]},{"url":"https://bugzilla.suse.com/1278429","tags":["report"]},{"url":"https://bugzilla.suse.com/1278430","tags":["report"]},{"url":"https://bugzilla.suse.com/1278431","tags":["report"]},{"url":"https://bugzilla.suse.com/1278704","tags":["report"]},{"url":"https://bugzilla.suse.com/1278711","tags":["report"]},{"url":"https://bugzilla.suse.com/1279455","tags":["report"]},{"url":"https://bugzilla.suse.com/1279464","tags":["report"]},{"url":"https://bugzilla.suse.com/1279467","tags":["report"]},{"url":"https://bugzilla.suse.com/1279468","tags":["report"]},{"url":"https://bugzilla.suse.com/1279471","tags":["report"]},{"url":"https://bugzilla.suse.com/1279477","tags":["report"]},{"url":"https://bugzilla.suse.com/1279483","tags":["report"]},{"url":"https://bugzilla.suse.com/1279485","tags":["report"]},{"url":"https://bugzilla.suse.com/1279493","tags":["report"]},{"url":"https://bugzilla.suse.com/1279494","tags":["report"]},{"url":"https://bugzilla.suse.com/1279496","tags":["report"]},{"url":"https://bugzilla.suse.com/1279499","tags":["report"]},{"url":"https://bugzilla.suse.com/1279504","tags":["report"]},{"url":"https://bugzilla.suse.com/1279508","tags":["report"]},{"url":"https://bugzilla.suse.com/1279510","tags":["report"]},{"url":"https://bugzilla.suse.com/1279520","tags":["report"]},{"url":"https://bugzilla.suse.com/1279533","tags":["report"]},{"url":"https://bugzilla.suse.com/1279564","tags":["report"]},{"url":"https://bugzilla.suse.com/1279592","tags":["report"]},{"url":"https://bugzilla.suse.com/1279594","tags":["report"]},{"url":"https://bugzilla.suse.com/1279605","tags":["report"]},{"url":"https://bugzilla.suse.com/1279606","tags":["report"]},{"url":"https://bugzilla.suse.com/1279607","tags":["report"]},{"url":"https://bugzilla.suse.com/1279608","tags":["report"]},{"url":"https://bugzilla.suse.com/1279614","tags":["report"]},{"url":"https://bugzilla.suse.com/1279616","tags":["report"]},{"url":"https://bugzilla.suse.com/1279624","tags":["report"]},{"url":"https://bugzilla.suse.com/1279625","tags":["report"]},{"url":"https://bugzilla.suse.com/1279627","tags":["report"]},{"url":"https://bugzilla.suse.com/1279632","tags":["report"]},{"url":"https://bugzilla.suse.com/1279698","tags":["report"]},{"url":"https://bugzilla.suse.com/1279699","tags":["report"]},{"url":"https://bugzilla.suse.com/1279777","tags":["report"]},{"url":"https://bugzilla.suse.com/1279795","tags":["report"]},{"url":"https://bugzilla.suse.com/1279798","tags":["report"]},{"url":"https://bugzilla.suse.com/1279802","tags":["report"]},{"url":"https://bugzilla.suse.com/1279805","tags":["report"]},{"url":"https://bugzilla.suse.com/1279808","tags":["report"]},{"url":"https://bugzilla.suse.com/1279809","tags":["report"]},{"url":"https://bugzilla.suse.com/1279812","tags":["report"]},{"url":"https://bugzilla.suse.com/1279814","tags":["report"]},{"url":"https://bugzilla.suse.com/1279815","tags":["report"]},{"url":"https://bugzilla.suse.com/1279816","tags":["report"]},{"url":"https://bugzilla.suse.com/1279825","tags":["report"]},{"url":"https://bugzilla.suse.com/1279920","tags":["report"]},{"url":"https://bugzilla.suse.com/1279921","tags":["report"]},{"url":"https://bugzilla.suse.com/1279971","tags":["report"]},{"url":"https://bugzilla.suse.com/1280141","tags":["report"]},{"url":"https://bugzilla.suse.com/1280142","tags":["report"]},{"url":"https://bugzilla.suse.com/1280156","tags":["report"]},{"url":"https://bugzilla.suse.com/1280157","tags":["report"]},{"url":"https://bugzilla.suse.com/1280158","tags":["report"]},{"url":"https://bugzilla.suse.com/1280162","tags":["report"]},{"url":"https://bugzilla.suse.com/1280172","tags":["report"]},{"url":"https://bugzilla.suse.com/1280178","tags":["report"]},{"url":"https://bugzilla.suse.com/1280185","tags":["report"]},{"url":"https://bugzilla.suse.com/1280215","tags":["report"]},{"url":"https://bugzilla.suse.com/1280221","tags":["report"]},{"url":"https://bugzilla.suse.com/1280230","tags":["report"]},{"url":"https://bugzilla.suse.com/1280234","tags":["report"]},{"url":"https://bugzilla.suse.com/1280244","tags":["report"]},{"url":"https://bugzilla.suse.com/1280246","tags":["report"]},{"url":"https://bugzilla.suse.com/1280247","tags":["report"]},{"url":"https://bugzilla.suse.com/1280251","tags":["report"]},{"url":"https://bugzilla.suse.com/1280253","tags":["report"]},{"url":"https://bugzilla.suse.com/1280266","tags":["report"]},{"url":"https://bugzilla.suse.com/1280273","tags":["report"]},{"url":"https://bugzilla.suse.com/1280276","tags":["report"]},{"url":"https://bugzilla.suse.com/1280301","tags":["report"]},{"url":"https://bugzilla.suse.com/1280305","tags":["report"]},{"url":"https://bugzilla.suse.com/1280306","tags":["report"]},{"url":"https://bugzilla.suse.com/1280311","tags":["report"]},{"url":"https://bugzilla.suse.com/1280315","tags":["report"]},{"url":"https://bugzilla.suse.com/1280316","tags":["report"]},{"url":"https://bugzilla.suse.com/1280319","tags":["report"]},{"url":"https://bugzilla.suse.com/1280345","tags":["report"]},{"url":"https://bugzilla.suse.com/1280378","tags":["report"]},{"url":"https://bugzilla.suse.com/1280395","tags":["report"]},{"url":"https://bugzilla.suse.com/1280397","tags":["report"]},{"url":"https://bugzilla.suse.com/1280398","tags":["report"]},{"url":"https://bugzilla.suse.com/1280399","tags":["report"]},{"url":"https://bugzilla.suse.com/1280400","tags":["report"]},{"url":"https://bugzilla.suse.com/1280402","tags":["report"]},{"url":"https://bugzilla.suse.com/1280408","tags":["report"]},{"url":"https://bugzilla.suse.com/1280410","tags":["report"]},{"url":"https://bugzilla.suse.com/1280415","tags":["report"]},{"url":"https://bugzilla.suse.com/1280416","tags":["report"]},{"url":"https://bugzilla.suse.com/1280421","tags":["report"]},{"url":"https://bugzilla.suse.com/1280423","tags":["report"]},{"url":"https://bugzilla.suse.com/1280425","tags":["report"]},{"url":"https://bugzilla.suse.com/1280428","tags":["report"]},{"url":"https://bugzilla.suse.com/1280429","tags":["report"]},{"url":"https://bugzilla.suse.com/1280431","tags":["report"]},{"url":"https://bugzilla.suse.com/1280434","tags":["report"]},{"url":"https://bugzilla.suse.com/1280463","tags":["report"]},{"url":"https://bugzilla.suse.com/1280472","tags":["report"]},{"url":"https://bugzilla.suse.com/1280476","tags":["report"]},{"url":"https://bugzilla.suse.com/1280477","tags":["report"]},{"url":"https://bugzilla.suse.com/1280479","tags":["report"]},{"url":"https://bugzilla.suse.com/1280480","tags":["report"]},{"url":"https://bugzilla.suse.com/1280492","tags":["report"]},{"url":"https://bugzilla.suse.com/1280500","tags":["report"]},{"url":"https://bugzilla.suse.com/1280501","tags":["report"]},{"url":"https://bugzilla.suse.com/1280504","tags":["report"]},{"url":"https://bugzilla.suse.com/1280505","tags":["report"]},{"url":"https://bugzilla.suse.com/1280520","tags":["report"]},{"url":"https://bugzilla.suse.com/1280539","tags":["report"]},{"url":"https://bugzilla.suse.com/1280545","tags":["report"]},{"url":"https://bugzilla.suse.com/1280554","tags":["report"]},{"url":"https://bugzilla.suse.com/1280559","tags":["report"]},{"url":"https://bugzilla.suse.com/1280560","tags":["report"]},{"url":"https://bugzilla.suse.com/1280563","tags":["report"]},{"url":"https://bugzilla.suse.com/1280569","tags":["report"]},{"url":"https://bugzilla.suse.com/1280570","tags":["report"]},{"url":"https://bugzilla.suse.com/1280571","tags":["report"]},{"url":"https://bugzilla.suse.com/1280573","tags":["report"]},{"url":"https://bugzilla.suse.com/1280581","tags":["report"]},{"url":"https://bugzilla.suse.com/1280713","tags":["report"]},{"url":"https://bugzilla.suse.com/1280735","tags":["report"]},{"url":"https://bugzilla.suse.com/1280736","tags":["report"]},{"url":"https://bugzilla.suse.com/1280745","tags":["report"]},{"url":"https://bugzilla.suse.com/1280777","tags":["report"]},{"url":"https://bugzilla.suse.com/1280785","tags":["report"]},{"url":"https://bugzilla.suse.com/1280794","tags":["report"]},{"url":"https://bugzilla.suse.com/1280804","tags":["report"]},{"url":"https://bugzilla.suse.com/1280806","tags":["report"]},{"url":"https://bugzilla.suse.com/1280813","tags":["report"]},{"url":"https://bugzilla.suse.com/1280822","tags":["report"]},{"url":"https://bugzilla.suse.com/1280826","tags":["report"]},{"url":"https://bugzilla.suse.com/1280834","tags":["report"]},{"url":"https://bugzilla.suse.com/1280918","tags":["report"]},{"url":"https://bugzilla.suse.com/1280948","tags":["report"]},{"url":"https://bugzilla.suse.com/1280960","tags":["report"]},{"url":"https://bugzilla.suse.com/1280970","tags":["report"]},{"url":"https://bugzilla.suse.com/1280976","tags":["report"]},{"url":"https://bugzilla.suse.com/1280977","tags":["report"]},{"url":"https://bugzilla.suse.com/1280978","tags":["report"]},{"url":"https://bugzilla.suse.com/1280980","tags":["report"]},{"url":"https://bugzilla.suse.com/1280981","tags":["report"]},{"url":"https://bugzilla.suse.com/1280984","tags":["report"]},{"url":"https://bugzilla.suse.com/1280987","tags":["report"]},{"url":"https://bugzilla.suse.com/1280992","tags":["report"]},{"url":"https://bugzilla.suse.com/1280996","tags":["report"]},{"url":"https://bugzilla.suse.com/1281001","tags":["report"]},{"url":"https://bugzilla.suse.com/1281003","tags":["report"]},{"url":"https://bugzilla.suse.com/1281005","tags":["report"]},{"url":"https://bugzilla.suse.com/1281008","tags":["report"]},{"url":"https://bugzilla.suse.com/1281011","tags":["report"]},{"url":"https://bugzilla.suse.com/1281018","tags":["report"]},{"url":"https://bugzilla.suse.com/1281022","tags":["report"]},{"url":"https://bugzilla.suse.com/1281027","tags":["report"]},{"url":"https://bugzilla.suse.com/1281029","tags":["report"]},{"url":"https://bugzilla.suse.com/1281030","tags":["report"]},{"url":"https://bugzilla.suse.com/1281034","tags":["report"]},{"url":"https://bugzilla.suse.com/1281052","tags":["report"]},{"url":"https://bugzilla.suse.com/1281056","tags":["report"]},{"url":"https://bugzilla.suse.com/1281058","tags":["report"]},{"url":"https://bugzilla.suse.com/1281065","tags":["report"]},{"url":"https://bugzilla.suse.com/1281130","tags":["report"]},{"url":"https://bugzilla.suse.com/1281138","tags":["report"]},{"url":"https://bugzilla.suse.com/1281149","tags":["report"]},{"url":"https://bugzilla.suse.com/1281150","tags":["report"]},{"url":"https://bugzilla.suse.com/1281151","tags":["report"]},{"url":"https://bugzilla.suse.com/1281155","tags":["report"]},{"url":"https://bugzilla.suse.com/1281156","tags":["report"]},{"url":"https://bugzilla.suse.com/1281163","tags":["report"]},{"url":"https://bugzilla.suse.com/1281164","tags":["report"]},{"url":"https://bugzilla.suse.com/1281165","tags":["report"]},{"url":"https://bugzilla.suse.com/1281173","tags":["report"]},{"url":"https://bugzilla.suse.com/1281174","tags":["report"]},{"url":"https://bugzilla.suse.com/1281179","tags":["report"]},{"url":"https://bugzilla.suse.com/1281180","tags":["report"]},{"url":"https://bugzilla.suse.com/1281181","tags":["report"]},{"url":"https://bugzilla.suse.com/1281183","tags":["report"]},{"url":"https://bugzilla.suse.com/1281184","tags":["report"]},{"url":"https://bugzilla.suse.com/1281185","tags":["report"]},{"url":"https://bugzilla.suse.com/1281189","tags":["report"]},{"url":"https://bugzilla.suse.com/1281190","tags":["report"]},{"url":"https://bugzilla.suse.com/1281191","tags":["report"]},{"url":"https://bugzilla.suse.com/1281194","tags":["report"]},{"url":"https://bugzilla.suse.com/1281204","tags":["report"]},{"url":"https://bugzilla.suse.com/1281206","tags":["report"]},{"url":"https://bugzilla.suse.com/1281211","tags":["report"]},{"url":"https://bugzilla.suse.com/1281214","tags":["report"]},{"url":"https://bugzilla.suse.com/1281216","tags":["report"]},{"url":"https://bugzilla.suse.com/1281221","tags":["report"]},{"url":"https://bugzilla.suse.com/1281222","tags":["report"]},{"url":"https://bugzilla.suse.com/1281251","tags":["report"]},{"url":"https://bugzilla.suse.com/1281253","tags":["report"]},{"url":"https://bugzilla.suse.com/1281254","tags":["report"]},{"url":"https://bugzilla.suse.com/1281257","tags":["report"]},{"url":"https://bugzilla.suse.com/1281260","tags":["report"]},{"url":"https://bugzilla.suse.com/1281265","tags":["report"]},{"url":"https://bugzilla.suse.com/1281269","tags":["report"]},{"url":"https://bugzilla.suse.com/1281270","tags":["report"]},{"url":"https://bugzilla.suse.com/1281271","tags":["report"]},{"url":"https://bugzilla.suse.com/1281272","tags":["report"]},{"url":"https://bugzilla.suse.com/1281275","tags":["report"]},{"url":"https://bugzilla.suse.com/1281277","tags":["report"]},{"url":"https://bugzilla.suse.com/1281281","tags":["report"]},{"url":"https://bugzilla.suse.com/1281292","tags":["report"]},{"url":"https://bugzilla.suse.com/1281299","tags":["report"]},{"url":"https://bugzilla.suse.com/1281300","tags":["report"]},{"url":"https://bugzilla.suse.com/1281311","tags":["report"]},{"url":"https://bugzilla.suse.com/1281315","tags":["report"]},{"url":"https://bugzilla.suse.com/1281320","tags":["report"]},{"url":"https://bugzilla.suse.com/1281332","tags":["report"]},{"url":"https://bugzilla.suse.com/1281333","tags":["report"]},{"url":"https://bugzilla.suse.com/1281334","tags":["report"]},{"url":"https://bugzilla.suse.com/1281337","tags":["report"]},{"url":"https://bugzilla.suse.com/1281346","tags":["report"]},{"url":"https://bugzilla.suse.com/1281352","tags":["report"]},{"url":"https://bugzilla.suse.com/1281353","tags":["report"]},{"url":"https://bugzilla.suse.com/1281357","tags":["report"]},{"url":"https://bugzilla.suse.com/1281360","tags":["report"]},{"url":"https://bugzilla.suse.com/1281361","tags":["report"]},{"url":"https://bugzilla.suse.com/1281363","tags":["report"]},{"url":"https://bugzilla.suse.com/1281368","tags":["report"]},{"url":"https://bugzilla.suse.com/1281382","tags":["report"]},{"url":"https://bugzilla.suse.com/1281384","tags":["report"]},{"url":"https://bugzilla.suse.com/1281391","tags":["report"]},{"url":"https://bugzilla.suse.com/1281392","tags":["report"]},{"url":"https://bugzilla.suse.com/1281394","tags":["report"]},{"url":"https://bugzilla.suse.com/1281395","tags":["report"]},{"url":"https://bugzilla.suse.com/1281396","tags":["report"]},{"url":"https://bugzilla.suse.com/1281402","tags":["report"]},{"url":"https://bugzilla.suse.com/1281418","tags":["report"]},{"url":"https://bugzilla.suse.com/1281422","tags":["report"]},{"url":"https://bugzilla.suse.com/1281429","tags":["report"]},{"url":"https://bugzilla.suse.com/1281488","tags":["report"]},{"url":"https://bugzilla.suse.com/1281490","tags":["report"]},{"url":"https://bugzilla.suse.com/1281495","tags":["report"]},{"url":"https://bugzilla.suse.com/1281500","tags":["report"]},{"url":"https://bugzilla.suse.com/1281504","tags":["report"]},{"url":"https://bugzilla.suse.com/1281509","tags":["report"]},{"url":"https://bugzilla.suse.com/1281510","tags":["report"]},{"url":"https://bugzilla.suse.com/1281535","tags":["report"]},{"url":"https://bugzilla.suse.com/1281538","tags":["report"]},{"url":"https://bugzilla.suse.com/1281547","tags":["report"]},{"url":"https://bugzilla.suse.com/1281549","tags":["report"]},{"url":"https://bugzilla.suse.com/1281551","tags":["report"]},{"url":"https://bugzilla.suse.com/1281563","tags":["report"]},{"url":"https://bugzilla.suse.com/1281568","tags":["report"]},{"url":"https://bugzilla.suse.com/1281577","tags":["report"]},{"url":"https://bugzilla.suse.com/1281579","tags":["report"]},{"url":"https://bugzilla.suse.com/1281619","tags":["report"]},{"url":"https://bugzilla.suse.com/1281620","tags":["report"]},{"url":"https://bugzilla.suse.com/1281626","tags":["report"]},{"url":"https://bugzilla.suse.com/1281631","tags":["report"]},{"url":"https://bugzilla.suse.com/1281635","tags":["report"]},{"url":"https://bugzilla.suse.com/1281639","tags":["report"]},{"url":"https://bugzilla.suse.com/1281640","tags":["report"]},{"url":"https://bugzilla.suse.com/1281650","tags":["report"]},{"url":"https://bugzilla.suse.com/1281672","tags":["report"]},{"url":"https://bugzilla.suse.com/1281676","tags":["report"]},{"url":"https://bugzilla.suse.com/1281677","tags":["report"]},{"url":"https://bugzilla.suse.com/1281688","tags":["report"]},{"url":"https://bugzilla.suse.com/1281691","tags":["report"]},{"url":"https://bugzilla.suse.com/1281696","tags":["report"]},{"url":"https://bugzilla.suse.com/1281701","tags":["report"]},{"url":"https://bugzilla.suse.com/1281702","tags":["report"]},{"url":"https://bugzilla.suse.com/1281705","tags":["report"]},{"url":"https://bugzilla.suse.com/1281706","tags":["report"]},{"url":"https://bugzilla.suse.com/1281707","tags":["report"]},{"url":"https://bugzilla.suse.com/1281708","tags":["report"]},{"url":"https://bugzilla.suse.com/1281715","tags":["report"]},{"url":"https://bugzilla.suse.com/1281723","tags":["report"]},{"url":"https://bugzilla.suse.com/1281724","tags":["report"]},{"url":"https://bugzilla.suse.com/1281735","tags":["report"]},{"url":"https://bugzilla.suse.com/1281736","tags":["report"]},{"url":"https://bugzilla.suse.com/1281753","tags":["report"]},{"url":"https://bugzilla.suse.com/1281776","tags":["report"]},{"url":"https://bugzilla.suse.com/1281779","tags":["report"]},{"url":"https://bugzilla.suse.com/1281781","tags":["report"]},{"url":"https://bugzilla.suse.com/1281783","tags":["report"]},{"url":"https://bugzilla.suse.com/1281784","tags":["report"]},{"url":"https://bugzilla.suse.com/1281785","tags":["report"]},{"url":"https://bugzilla.suse.com/1281796","tags":["report"]},{"url":"https://bugzilla.suse.com/1281799","tags":["report"]},{"url":"https://bugzilla.suse.com/1281801","tags":["report"]},{"url":"https://bugzilla.suse.com/1281804","tags":["report"]},{"url":"https://bugzilla.suse.com/1281813","tags":["report"]},{"url":"https://bugzilla.suse.com/1281824","tags":["report"]},{"url":"https://bugzilla.suse.com/1281828","tags":["report"]},{"url":"https://bugzilla.suse.com/1281850","tags":["report"]},{"url":"https://bugzilla.suse.com/1281851","tags":["report"]},{"url":"https://bugzilla.suse.com/1281853","tags":["report"]},{"url":"https://bugzilla.suse.com/1281858","tags":["report"]},{"url":"https://bugzilla.suse.com/1281868","tags":["report"]},{"url":"https://bugzilla.suse.com/1281870","tags":["report"]},{"url":"https://bugzilla.suse.com/1281877","tags":["report"]},{"url":"https://bugzilla.suse.com/1281886","tags":["report"]},{"url":"https://bugzilla.suse.com/1281887","tags":["report"]},{"url":"https://bugzilla.suse.com/1281890","tags":["report"]},{"url":"https://bugzilla.suse.com/1281891","tags":["report"]},{"url":"https://bugzilla.suse.com/1281895","tags":["report"]},{"url":"https://bugzilla.suse.com/1281897","tags":["report"]},{"url":"https://bugzilla.suse.com/1281900","tags":["report"]},{"url":"https://bugzilla.suse.com/1281903","tags":["report"]},{"url":"https://bugzilla.suse.com/1281916","tags":["report"]},{"url":"https://bugzilla.suse.com/1281930","tags":["report"]},{"url":"https://bugzilla.suse.com/1281932","tags":["report"]},{"url":"https://bugzilla.suse.com/1281968","tags":["report"]},{"url":"https://bugzilla.suse.com/1281969","tags":["report"]},{"url":"https://bugzilla.suse.com/1281985","tags":["report"]},{"url":"https://bugzilla.suse.com/1281987","tags":["report"]},{"url":"https://bugzilla.suse.com/1281996","tags":["report"]},{"url":"https://bugzilla.suse.com/1282001","tags":["report"]},{"url":"https://bugzilla.suse.com/1282002","tags":["report"]},{"url":"https://bugzilla.suse.com/1282008","tags":["report"]},{"url":"https://bugzilla.suse.com/1282018","tags":["report"]},{"url":"https://bugzilla.suse.com/1282019","tags":["report"]},{"url":"https://bugzilla.suse.com/1282021","tags":["report"]},{"url":"https://bugzilla.suse.com/1282025","tags":["report"]},{"url":"https://bugzilla.suse.com/1282026","tags":["report"]},{"url":"https://bugzilla.suse.com/1282027","tags":["report"]},{"url":"https://bugzilla.suse.com/1282031","tags":["report"]},{"url":"https://bugzilla.suse.com/1282032","tags":["report"]},{"url":"https://bugzilla.suse.com/1282033","tags":["report"]},{"url":"https://bugzilla.suse.com/1282044","tags":["report"]},{"url":"https://bugzilla.suse.com/1282045","tags":["report"]},{"url":"https://bugzilla.suse.com/1282063","tags":["report"]},{"url":"https://bugzilla.suse.com/1282065","tags":["report"]},{"url":"https://bugzilla.suse.com/1282068","tags":["report"]},{"url":"https://bugzilla.suse.com/1282080","tags":["report"]},{"url":"https://bugzilla.suse.com/1282081","tags":["report"]},{"url":"https://bugzilla.suse.com/1282082","tags":["report"]},{"url":"https://bugzilla.suse.com/1282083","tags":["report"]},{"url":"https://bugzilla.suse.com/1282095","tags":["report"]},{"url":"https://bugzilla.suse.com/1282114","tags":["report"]},{"url":"https://bugzilla.suse.com/1282116","tags":["report"]},{"url":"https://bugzilla.suse.com/1282117","tags":["report"]},{"url":"https://bugzilla.suse.com/1282122","tags":["report"]},{"url":"https://bugzilla.suse.com/1282128","tags":["report"]},{"url":"https://bugzilla.suse.com/1282133","tags":["report"]},{"url":"https://bugzilla.suse.com/1282134","tags":["report"]},{"url":"https://bugzilla.suse.com/1282145","tags":["report"]},{"url":"https://bugzilla.suse.com/1282146","tags":["report"]},{"url":"https://bugzilla.suse.com/1282149","tags":["report"]},{"url":"https://bugzilla.suse.com/1282151","tags":["report"]},{"url":"https://bugzilla.suse.com/1282154","tags":["report"]},{"url":"https://bugzilla.suse.com/1282156","tags":["report"]},{"url":"https://bugzilla.suse.com/1282158","tags":["report"]},{"url":"https://bugzilla.suse.com/1282167","tags":["report"]},{"url":"https://bugzilla.suse.com/1282174","tags":["report"]},{"url":"https://bugzilla.suse.com/1282178","tags":["report"]},{"url":"https://bugzilla.suse.com/1282189","tags":["report"]},{"url":"https://bugzilla.suse.com/1282192","tags":["report"]},{"url":"https://bugzilla.suse.com/1282196","tags":["report"]},{"url":"https://bugzilla.suse.com/1282262","tags":["report"]},{"url":"https://bugzilla.suse.com/1282276","tags":["report"]},{"url":"https://bugzilla.suse.com/1282289","tags":["report"]},{"url":"https://bugzilla.suse.com/1282296","tags":["report"]},{"url":"https://bugzilla.suse.com/1282298","tags":["report"]},{"url":"https://bugzilla.suse.com/1282302","tags":["report"]},{"url":"https://bugzilla.suse.com/1282304","tags":["report"]},{"url":"https://bugzilla.suse.com/1282325","tags":["report"]},{"url":"https://bugzilla.suse.com/1282327","tags":["report"]},{"url":"https://bugzilla.suse.com/1282328","tags":["report"]},{"url":"https://bugzilla.suse.com/1282677","tags":["report"]},{"url":"https://bugzilla.suse.com/1282684","tags":["report"]},{"url":"https://bugzilla.suse.com/1282686","tags":["report"]},{"url":"https://bugzilla.suse.com/1282690","tags":["report"]},{"url":"https://bugzilla.suse.com/1282691","tags":["report"]},{"url":"https://bugzilla.suse.com/1282695","tags":["report"]},{"url":"https://bugzilla.suse.com/1282697","tags":["report"]},{"url":"https://bugzilla.suse.com/1282729","tags":["report"]},{"url":"https://bugzilla.suse.com/1282737","tags":["report"]},{"url":"https://bugzilla.suse.com/1282744","tags":["report"]},{"url":"https://bugzilla.suse.com/1282753","tags":["report"]},{"url":"https://bugzilla.suse.com/1282754","tags":["report"]},{"url":"https://bugzilla.suse.com/1282759","tags":["report"]},{"url":"https://bugzilla.suse.com/1282763","tags":["report"]},{"url":"https://bugzilla.suse.com/1282764","tags":["report"]},{"url":"https://bugzilla.suse.com/1282772","tags":["report"]},{"url":"https://bugzilla.suse.com/1282773","tags":["report"]},{"url":"https://bugzilla.suse.com/1282775","tags":["report"]},{"url":"https://bugzilla.suse.com/1282776","tags":["report"]},{"url":"https://bugzilla.suse.com/1282778","tags":["report"]},{"url":"https://bugzilla.suse.com/1282805","tags":["report"]},{"url":"https://bugzilla.suse.com/1282814","tags":["report"]},{"url":"https://bugzilla.suse.com/1282867","tags":["report"]},{"url":"https://bugzilla.suse.com/1282870","tags":["report"]},{"url":"https://bugzilla.suse.com/1282879","tags":["report"]},{"url":"https://bugzilla.suse.com/1282885","tags":["report"]},{"url":"https://bugzilla.suse.com/1282887","tags":["report"]},{"url":"https://bugzilla.suse.com/1282889","tags":["report"]},{"url":"https://bugzilla.suse.com/1282890","tags":["report"]},{"url":"https://bugzilla.suse.com/1282893","tags":["report"]},{"url":"https://bugzilla.suse.com/1282898","tags":["report"]},{"url":"https://bugzilla.suse.com/1282911","tags":["report"]},{"url":"https://bugzilla.suse.com/1282914","tags":["report"]},{"url":"https://bugzilla.suse.com/1282915","tags":["report"]},{"url":"https://bugzilla.suse.com/1282920","tags":["report"]},{"url":"https://bugzilla.suse.com/1282924","tags":["report"]},{"url":"https://bugzilla.suse.com/1282925","tags":["report"]},{"url":"https://bugzilla.suse.com/1282926","tags":["report"]},{"url":"https://bugzilla.suse.com/1282927","tags":["report"]},{"url":"https://bugzilla.suse.com/1282935","tags":["report"]},{"url":"https://bugzilla.suse.com/1282955","tags":["report"]},{"url":"https://bugzilla.suse.com/1282957","tags":["report"]},{"url":"https://bugzilla.suse.com/1282962","tags":["report"]},{"url":"https://bugzilla.suse.com/1282963","tags":["report"]},{"url":"https://bugzilla.suse.com/1282974","tags":["report"]},{"url":"https://bugzilla.suse.com/1282984","tags":["report"]},{"url":"https://bugzilla.suse.com/1283004","tags":["report"]},{"url":"https://bugzilla.suse.com/1283016","tags":["report"]},{"url":"https://bugzilla.suse.com/1283017","tags":["report"]},{"url":"https://bugzilla.suse.com/1283018","tags":["report"]},{"url":"https://bugzilla.suse.com/1283036","tags":["report"]},{"url":"https://bugzilla.suse.com/1283039","tags":["report"]},{"url":"https://bugzilla.suse.com/1283045","tags":["report"]},{"url":"https://bugzilla.suse.com/1283047","tags":["report"]},{"url":"https://bugzilla.suse.com/1283051","tags":["report"]},{"url":"https://bugzilla.suse.com/1283058","tags":["report"]},{"url":"https://bugzilla.suse.com/1283076","tags":["report"]},{"url":"https://bugzilla.suse.com/1283077","tags":["report"]},{"url":"https://bugzilla.suse.com/1283078","tags":["report"]},{"url":"https://bugzilla.suse.com/1283081","tags":["report"]},{"url":"https://bugzilla.suse.com/1283087","tags":["report"]},{"url":"https://bugzilla.suse.com/1283113","tags":["report"]},{"url":"https://bugzilla.suse.com/1283114","tags":["report"]},{"url":"https://bugzilla.suse.com/1283122","tags":["report"]},{"url":"https://bugzilla.suse.com/1283132","tags":["report"]},{"url":"https://bugzilla.suse.com/1283134","tags":["report"]},{"url":"https://bugzilla.suse.com/1283136","tags":["report"]},{"url":"https://bugzilla.suse.com/1283145","tags":["report"]},{"url":"https://bugzilla.suse.com/1283155","tags":["report"]},{"url":"https://bugzilla.suse.com/1283157","tags":["report"]},{"url":"https://bugzilla.suse.com/1283159","tags":["report"]},{"url":"https://bugzilla.suse.com/1283164","tags":["report"]},{"url":"https://bugzilla.suse.com/1283175","tags":["report"]},{"url":"https://bugzilla.suse.com/1283177","tags":["report"]},{"url":"https://bugzilla.suse.com/1283196","tags":["report"]},{"url":"https://bugzilla.suse.com/1283197","tags":["report"]},{"url":"https://bugzilla.suse.com/1283202","tags":["report"]},{"url":"https://bugzilla.suse.com/1283206","tags":["report"]},{"url":"https://bugzilla.suse.com/1283208","tags":["report"]},{"url":"https://bugzilla.suse.com/1283209","tags":["report"]},{"url":"https://bugzilla.suse.com/1283211","tags":["report"]},{"url":"https://bugzilla.suse.com/1283214","tags":["report"]},{"url":"https://bugzilla.suse.com/1283215","tags":["report"]},{"url":"https://bugzilla.suse.com/1283220","tags":["report"]},{"url":"https://bugzilla.suse.com/1283223","tags":["report"]},{"url":"https://bugzilla.suse.com/1283224","tags":["report"]},{"url":"https://bugzilla.suse.com/1283225","tags":["report"]},{"url":"https://bugzilla.suse.com/1283226","tags":["report"]},{"url":"https://bugzilla.suse.com/1283229","tags":["report"]},{"url":"https://bugzilla.suse.com/1283231","tags":["report"]},{"url":"https://bugzilla.suse.com/1283271","tags":["report"]},{"url":"https://bugzilla.suse.com/1283276","tags":["report"]},{"url":"https://bugzilla.suse.com/1283278","tags":["report"]},{"url":"https://bugzilla.suse.com/1283287","tags":["report"]},{"url":"https://bugzilla.suse.com/1283288","tags":["report"]},{"url":"https://bugzilla.suse.com/1283292","tags":["report"]},{"url":"https://bugzilla.suse.com/1283333","tags":["report"]},{"url":"https://bugzilla.suse.com/1283334","tags":["report"]},{"url":"https://bugzilla.suse.com/1283335","tags":["report"]},{"url":"https://bugzilla.suse.com/1283337","tags":["report"]},{"url":"https://bugzilla.suse.com/1283339","tags":["report"]},{"url":"https://bugzilla.suse.com/1283343","tags":["report"]},{"url":"https://bugzilla.suse.com/1283349","tags":["report"]},{"url":"https://bugzilla.suse.com/1283356","tags":["report"]},{"url":"https://bugzilla.suse.com/1283360","tags":["report"]},{"url":"https://bugzilla.suse.com/1283364","tags":["report"]},{"url":"https://bugzilla.suse.com/1283416","tags":["report"]},{"url":"https://bugzilla.suse.com/1283418","tags":["report"]},{"url":"https://bugzilla.suse.com/1283429","tags":["report"]},{"url":"https://bugzilla.suse.com/1283445","tags":["report"]},{"url":"https://bugzilla.suse.com/1283453","tags":["report"]},{"url":"https://bugzilla.suse.com/1283464","tags":["report"]},{"url":"https://bugzilla.suse.com/1283469","tags":["report"]},{"url":"https://bugzilla.suse.com/1283474","tags":["report"]},{"url":"https://bugzilla.suse.com/1283481","tags":["report"]},{"url":"https://bugzilla.suse.com/1283483","tags":["report"]},{"url":"https://bugzilla.suse.com/1283485","tags":["report"]},{"url":"https://bugzilla.suse.com/1283486","tags":["report"]},{"url":"https://bugzilla.suse.com/1283502","tags":["report"]},{"url":"https://bugzilla.suse.com/1283511","tags":["report"]},{"url":"https://bugzilla.suse.com/1283585","tags":["report"]},{"url":"https://bugzilla.suse.com/1283662","tags":["report"]},{"url":"https://bugzilla.suse.com/1283668","tags":["report"]},{"url":"https://bugzilla.suse.com/1283741","tags":["report"]},{"url":"https://bugzilla.suse.com/1283746","tags":["report"]},{"url":"https://bugzilla.suse.com/1283752","tags":["report"]},{"url":"https://bugzilla.suse.com/1283754","tags":["report"]},{"url":"https://bugzilla.suse.com/1283782","tags":["report"]},{"url":"https://bugzilla.suse.com/1283793","tags":["report"]},{"url":"https://bugzilla.suse.com/1283810","tags":["report"]},{"url":"https://bugzilla.suse.com/1283821","tags":["report"]},{"url":"https://bugzilla.suse.com/1283830","tags":["report"]},{"url":"https://bugzilla.suse.com/1283833","tags":["report"]},{"url":"https://bugzilla.suse.com/1283834","tags":["report"]},{"url":"https://bugzilla.suse.com/1283837","tags":["report"]},{"url":"https://bugzilla.suse.com/1283838","tags":["report"]},{"url":"https://bugzilla.suse.com/1283842","tags":["report"]},{"url":"https://bugzilla.suse.com/1283844","tags":["report"]},{"url":"https://bugzilla.suse.com/1283845","tags":["report"]},{"url":"https://bugzilla.suse.com/1283846","tags":["report"]},{"url":"https://bugzilla.suse.com/1283863","tags":["report"]},{"url":"https://bugzilla.suse.com/1283869","tags":["report"]},{"url":"https://bugzilla.suse.com/1283871","tags":["report"]},{"url":"https://bugzilla.suse.com/1283878","tags":["report"]},{"url":"https://bugzilla.suse.com/1283884","tags":["report"]},{"url":"https://bugzilla.suse.com/1283886","tags":["report"]},{"url":"https://bugzilla.suse.com/1283903","tags":["report"]},{"url":"https://bugzilla.suse.com/1283916","tags":["report"]},{"url":"https://bugzilla.suse.com/1283920","tags":["report"]},{"url":"https://bugzilla.suse.com/1283921","tags":["report"]},{"url":"https://bugzilla.suse.com/1283928","tags":["report"]},{"url":"https://bugzilla.suse.com/1283933","tags":["report"]},{"url":"https://bugzilla.suse.com/1283941","tags":["report"]},{"url":"https://bugzilla.suse.com/1283958","tags":["report"]},{"url":"https://bugzilla.suse.com/1283960","tags":["report"]},{"url":"https://bugzilla.suse.com/1283967","tags":["report"]},{"url":"https://bugzilla.suse.com/1284024","tags":["report"]},{"url":"https://bugzilla.suse.com/1284031","tags":["report"]},{"url":"https://bugzilla.suse.com/1284150","tags":["report"]},{"url":"https://bugzilla.suse.com/1284243","tags":["report"]},{"url":"https://bugzilla.suse.com/1284292","tags":["report"]},{"url":"https://bugzilla.suse.com/1284293","tags":["report"]},{"url":"https://bugzilla.suse.com/1284296","tags":["report"]},{"url":"https://bugzilla.suse.com/1284302","tags":["report"]},{"url":"https://bugzilla.suse.com/1284304","tags":["report"]},{"url":"https://bugzilla.suse.com/1284305","tags":["report"]},{"url":"https://bugzilla.suse.com/1284313","tags":["report"]},{"url":"https://bugzilla.suse.com/1284346","tags":["report"]},{"url":"https://bugzilla.suse.com/1284349","tags":["report"]},{"url":"https://bugzilla.suse.com/1284350","tags":["report"]},{"url":"https://bugzilla.suse.com/1284358","tags":["report"]},{"url":"https://bugzilla.suse.com/1284360","tags":["report"]},{"url":"https://bugzilla.suse.com/1284363","tags":["report"]},{"url":"https://bugzilla.suse.com/1284446","tags":["report"]},{"url":"https://bugzilla.suse.com/1284455","tags":["report"]},{"url":"https://bugzilla.suse.com/1284477","tags":["report"]},{"url":"https://bugzilla.suse.com/1284483","tags":["report"]},{"url":"https://bugzilla.suse.com/1284484","tags":["report"]},{"url":"https://bugzilla.suse.com/1284485","tags":["report"]},{"url":"https://bugzilla.suse.com/1284498","tags":["report"]},{"url":"https://bugzilla.suse.com/1284503","tags":["report"]},{"url":"https://bugzilla.suse.com/1284504","tags":["report"]},{"url":"https://bugzilla.suse.com/1284505","tags":["report"]},{"url":"https://bugzilla.suse.com/1284509","tags":["report"]},{"url":"https://bugzilla.suse.com/1284512","tags":["report"]},{"url":"https://bugzilla.suse.com/1284513","tags":["report"]},{"url":"https://bugzilla.suse.com/1284514","tags":["report"]},{"url":"https://bugzilla.suse.com/1284515","tags":["report"]},{"url":"https://bugzilla.suse.com/1284517","tags":["report"]},{"url":"https://bugzilla.suse.com/1284537","tags":["report"]},{"url":"https://bugzilla.suse.com/1284540","tags":["report"]},{"url":"https://bugzilla.suse.com/1284541","tags":["report"]},{"url":"https://bugzilla.suse.com/1284542","tags":["report"]},{"url":"https://bugzilla.suse.com/1284543","tags":["report"]},{"url":"https://bugzilla.suse.com/1284544","tags":["report"]},{"url":"https://bugzilla.suse.com/1284545","tags":["report"]},{"url":"https://bugzilla.suse.com/1284553","tags":["report"]},{"url":"https://bugzilla.suse.com/1284554","tags":["report"]},{"url":"https://bugzilla.suse.com/1284555","tags":["report"]},{"url":"https://bugzilla.suse.com/1284557","tags":["report"]},{"url":"https://bugzilla.suse.com/1284563","tags":["report"]},{"url":"https://bugzilla.suse.com/1284568","tags":["report"]},{"url":"https://bugzilla.suse.com/1284577","tags":["report"]},{"url":"https://bugzilla.suse.com/1284578","tags":["report"]},{"url":"https://bugzilla.suse.com/1284579","tags":["report"]},{"url":"https://bugzilla.suse.com/1284584","tags":["report"]},{"url":"https://bugzilla.suse.com/1284595","tags":["report"]},{"url":"https://bugzilla.suse.com/1284601","tags":["report"]},{"url":"https://bugzilla.suse.com/1284602","tags":["report"]},{"url":"https://bugzilla.suse.com/1284609","tags":["report"]},{"url":"https://bugzilla.suse.com/1284615","tags":["report"]},{"url":"https://bugzilla.suse.com/1284616","tags":["report"]},{"url":"https://bugzilla.suse.com/1284620","tags":["report"]},{"url":"https://bugzilla.suse.com/1284621","tags":["report"]},{"url":"https://bugzilla.suse.com/1284623","tags":["report"]},{"url":"https://bugzilla.suse.com/1284626","tags":["report"]},{"url":"https://bugzilla.suse.com/1284630","tags":["report"]},{"url":"https://bugzilla.suse.com/1284631","tags":["report"]},{"url":"https://bugzilla.suse.com/1284635","tags":["report"]},{"url":"https://bugzilla.suse.com/1284636","tags":["report"]},{"url":"https://bugzilla.suse.com/1284637","tags":["report"]},{"url":"https://bugzilla.suse.com/1284638","tags":["report"]},{"url":"https://bugzilla.suse.com/1284640","tags":["report"]},{"url":"https://bugzilla.suse.com/1284641","tags":["report"]},{"url":"https://bugzilla.suse.com/1284643","tags":["report"]},{"url":"https://bugzilla.suse.com/1284644","tags":["report"]},{"url":"https://bugzilla.suse.com/1284652","tags":["report"]},{"url":"https://bugzilla.suse.com/1284704","tags":["report"]},{"url":"https://bugzilla.suse.com/1284706","tags":["report"]},{"url":"https://bugzilla.suse.com/1284707","tags":["report"]},{"url":"https://bugzilla.suse.com/1284709","tags":["report"]},{"url":"https://bugzilla.suse.com/1284721","tags":["report"]},{"url":"https://bugzilla.suse.com/1284723","tags":["report"]},{"url":"https://bugzilla.suse.com/1284740","tags":["report"]},{"url":"https://bugzilla.suse.com/1285553","tags":["report"]},{"url":"https://bugzilla.suse.com/1285556","tags":["report"]},{"url":"https://bugzilla.suse.com/1285560","tags":["report"]},{"url":"https://bugzilla.suse.com/1285561","tags":["report"]},{"url":"https://bugzilla.suse.com/1285562","tags":["report"]},{"url":"https://bugzilla.suse.com/1285564","tags":["report"]},{"url":"https://bugzilla.suse.com/1285569","tags":["report"]},{"url":"https://bugzilla.suse.com/1285587","tags":["report"]},{"url":"https://bugzilla.suse.com/1285624","tags":["report"]},{"url":"https://bugzilla.suse.com/1285648","tags":["report"]},{"url":"https://bugzilla.suse.com/1285668","tags":["report"]},{"url":"https://bugzilla.suse.com/1285914","tags":["report"]},{"url":"https://bugzilla.suse.com/1285957","tags":["report"]},{"url":"https://bugzilla.suse.com/1285971","tags":["report"]},{"url":"https://bugzilla.suse.com/1285976","tags":["report"]},{"url":"https://bugzilla.suse.com/1285978","tags":["report"]},{"url":"https://bugzilla.suse.com/1285979","tags":["report"]},{"url":"https://bugzilla.suse.com/1285985","tags":["report"]},{"url":"https://bugzilla.suse.com/1285988","tags":["report"]},{"url":"https://bugzilla.suse.com/1285998","tags":["report"]},{"url":"https://bugzilla.suse.com/1286009","tags":["report"]},{"url":"https://bugzilla.suse.com/1286012","tags":["report"]},{"url":"https://bugzilla.suse.com/1286013","tags":["report"]},{"url":"https://bugzilla.suse.com/1286019","tags":["report"]},{"url":"https://bugzilla.suse.com/1286036","tags":["report"]},{"url":"https://bugzilla.suse.com/1286037","tags":["report"]},{"url":"https://bugzilla.suse.com/1286112","tags":["report"]},{"url":"https://bugzilla.suse.com/1286114","tags":["report"]},{"url":"https://bugzilla.suse.com/1286119","tags":["report"]},{"url":"https://bugzilla.suse.com/1286121","tags":["report"]},{"url":"https://bugzilla.suse.com/1286123","tags":["report"]},{"url":"https://bugzilla.suse.com/1286158","tags":["report"]},{"url":"https://bugzilla.suse.com/1286160","tags":["report"]},{"url":"https://bugzilla.suse.com/1286161","tags":["report"]},{"url":"https://bugzilla.suse.com/1286171","tags":["report"]},{"url":"https://bugzilla.suse.com/1286190","tags":["report"]},{"url":"https://bugzilla.suse.com/1286204","tags":["report"]},{"url":"https://bugzilla.suse.com/1286205","tags":["report"]},{"url":"https://bugzilla.suse.com/1286207","tags":["report"]},{"url":"https://bugzilla.suse.com/1286215","tags":["report"]},{"url":"https://bugzilla.suse.com/1286217","tags":["report"]},{"url":"https://bugzilla.suse.com/1286224","tags":["report"]},{"url":"https://bugzilla.suse.com/1286233","tags":["report"]},{"url":"https://bugzilla.suse.com/1286234","tags":["report"]},{"url":"https://bugzilla.suse.com/1286237","tags":["report"]},{"url":"https://bugzilla.suse.com/1286240","tags":["report"]},{"url":"https://bugzilla.suse.com/1286257","tags":["report"]},{"url":"https://bugzilla.suse.com/1286259","tags":["report"]},{"url":"https://bugzilla.suse.com/1286267","tags":["report"]},{"url":"https://bugzilla.suse.com/1286342","tags":["report"]},{"url":"https://bugzilla.suse.com/1286346","tags":["report"]},{"url":"https://bugzilla.suse.com/1286390","tags":["report"]},{"url":"https://bugzilla.suse.com/1286391","tags":["report"]},{"url":"https://bugzilla.suse.com/1286394","tags":["report"]},{"url":"https://bugzilla.suse.com/1286417","tags":["report"]},{"url":"https://bugzilla.suse.com/1286421","tags":["report"]},{"url":"https://bugzilla.suse.com/1286431","tags":["report"]},{"url":"https://bugzilla.suse.com/1286432","tags":["report"]},{"url":"https://bugzilla.suse.com/1286443","tags":["report"]},{"url":"https://bugzilla.suse.com/1286444","tags":["report"]},{"url":"https://bugzilla.suse.com/1286453","tags":["report"]},{"url":"https://bugzilla.suse.com/1286455","tags":["report"]},{"url":"https://bugzilla.suse.com/1286457","tags":["report"]},{"url":"https://bugzilla.suse.com/1286469","tags":["report"]},{"url":"https://bugzilla.suse.com/1286514","tags":["report"]},{"url":"https://bugzilla.suse.com/1286529","tags":["report"]},{"url":"https://bugzilla.suse.com/1286625","tags":["report"]},{"url":"https://bugzilla.suse.com/1286654","tags":["report"]},{"url":"https://bugzilla.suse.com/1286669","tags":["report"]},{"url":"https://bugzilla.suse.com/1286671","tags":["report"]},{"url":"https://bugzilla.suse.com/1286672","tags":["report"]},{"url":"https://bugzilla.suse.com/1286689","tags":["report"]},{"url":"https://bugzilla.suse.com/1286692","tags":["report"]},{"url":"https://bugzilla.suse.com/1286704","tags":["report"]},{"url":"https://bugzilla.suse.com/1286707","tags":["report"]},{"url":"https://bugzilla.suse.com/1286713","tags":["report"]},{"url":"https://bugzilla.suse.com/1286720","tags":["report"]},{"url":"https://bugzilla.suse.com/1286735","tags":["report"]},{"url":"https://bugzilla.suse.com/1286741","tags":["report"]},{"url":"https://bugzilla.suse.com/1286742","tags":["report"]},{"url":"https://bugzilla.suse.com/1286756","tags":["report"]},{"url":"https://bugzilla.suse.com/1286757","tags":["report"]},{"url":"https://bugzilla.suse.com/1286772","tags":["report"]},{"url":"https://bugzilla.suse.com/1286775","tags":["report"]},{"url":"https://bugzilla.suse.com/1286778","tags":["report"]},{"url":"https://bugzilla.suse.com/1286782","tags":["report"]},{"url":"https://bugzilla.suse.com/1286785","tags":["report"]},{"url":"https://bugzilla.suse.com/1286787","tags":["report"]},{"url":"https://bugzilla.suse.com/1286819","tags":["report"]},{"url":"https://bugzilla.suse.com/1286820","tags":["report"]},{"url":"https://bugzilla.suse.com/1286821","tags":["report"]},{"url":"https://bugzilla.suse.com/1286822","tags":["report"]},{"url":"https://bugzilla.suse.com/1286823","tags":["report"]},{"url":"https://bugzilla.suse.com/1286824","tags":["report"]},{"url":"https://bugzilla.suse.com/1286841","tags":["report"]},{"url":"https://bugzilla.suse.com/1286843","tags":["report"]},{"url":"https://bugzilla.suse.com/1286850","tags":["report"]},{"url":"https://bugzilla.suse.com/1286856","tags":["report"]},{"url":"https://bugzilla.suse.com/1286857","tags":["report"]},{"url":"https://bugzilla.suse.com/1286859","tags":["report"]},{"url":"https://bugzilla.suse.com/1286860","tags":["report"]},{"url":"https://bugzilla.suse.com/1286862","tags":["report"]},{"url":"https://bugzilla.suse.com/1286863","tags":["report"]},{"url":"https://bugzilla.suse.com/1286864","tags":["report"]},{"url":"https://bugzilla.suse.com/1286865","tags":["report"]},{"url":"https://bugzilla.suse.com/1286867","tags":["report"]},{"url":"https://bugzilla.suse.com/1286872","tags":["report"]},{"url":"https://bugzilla.suse.com/1286874","tags":["report"]},{"url":"https://bugzilla.suse.com/1286877","tags":["report"]},{"url":"https://bugzilla.suse.com/1286890","tags":["report"]},{"url":"https://bugzilla.suse.com/1286913","tags":["report"]},{"url":"https://bugzilla.suse.com/1286918","tags":["report"]},{"url":"https://bugzilla.suse.com/1286919","tags":["report"]},{"url":"https://bugzilla.suse.com/1287173","tags":["report"]},{"url":"https://bugzilla.suse.com/1287191","tags":["report"]},{"url":"https://bugzilla.suse.com/1287256","tags":["report"]},{"url":"https://bugzilla.suse.com/1287268","tags":["report"]},{"url":"https://bugzilla.suse.com/1287342","tags":["report"]},{"url":"https://bugzilla.suse.com/1287346","tags":["report"]},{"url":"https://bugzilla.suse.com/1287347","tags":["report"]},{"url":"https://bugzilla.suse.com/1287351","tags":["report"]},{"url":"https://bugzilla.suse.com/1287364","tags":["report"]},{"url":"https://bugzilla.suse.com/1287592","tags":["report"]},{"url":"https://bugzilla.suse.com/1287594","tags":["report"]},{"url":"https://bugzilla.suse.com/1287597","tags":["report"]},{"url":"https://bugzilla.suse.com/1287648","tags":["report"]},{"url":"https://bugzilla.suse.com/1287649","tags":["report"]},{"url":"https://bugzilla.suse.com/1287655","tags":["report"]},{"url":"https://bugzilla.suse.com/1287658","tags":["report"]},{"url":"https://bugzilla.suse.com/1287674","tags":["report"]},{"url":"https://bugzilla.suse.com/1287680","tags":["report"]},{"url":"https://bugzilla.suse.com/1287682","tags":["report"]},{"url":"https://bugzilla.suse.com/1287714","tags":["report"]},{"url":"https://bugzilla.suse.com/1287719","tags":["report"]},{"url":"https://bugzilla.suse.com/1287720","tags":["report"]},{"url":"https://bugzilla.suse.com/1287737","tags":["report"]},{"url":"https://bugzilla.suse.com/1287749","tags":["report"]},{"url":"https://bugzilla.suse.com/1287757","tags":["report"]},{"url":"https://bugzilla.suse.com/1287765","tags":["report"]},{"url":"https://bugzilla.suse.com/1287773","tags":["report"]},{"url":"https://bugzilla.suse.com/1287774","tags":["report"]},{"url":"https://bugzilla.suse.com/1287966","tags":["report"]},{"url":"https://bugzilla.suse.com/1287984","tags":["report"]},{"url":"https://bugzilla.suse.com/1287985","tags":["report"]},{"url":"https://bugzilla.suse.com/1287995","tags":["report"]},{"url":"https://bugzilla.suse.com/1288001","tags":["report"]},{"url":"https://bugzilla.suse.com/1288002","tags":["report"]},{"url":"https://bugzilla.suse.com/1288005","tags":["report"]},{"url":"https://bugzilla.suse.com/1288007","tags":["report"]},{"url":"https://bugzilla.suse.com/1288014","tags":["report"]},{"url":"https://bugzilla.suse.com/1288061","tags":["report"]},{"url":"https://bugzilla.suse.com/1288088","tags":["report"]},{"url":"https://bugzilla.suse.com/1288125","tags":["report"]},{"url":"https://bugzilla.suse.com/1288127","tags":["report"]},{"url":"https://bugzilla.suse.com/1288246","tags":["report"]},{"url":"https://bugzilla.suse.com/1288248","tags":["report"]},{"url":"https://bugzilla.suse.com/1288521","tags":["report"]},{"url":"https://bugzilla.suse.com/1288522","tags":["report"]},{"url":"https://bugzilla.suse.com/1288527","tags":["report"]},{"url":"https://bugzilla.suse.com/1288584","tags":["report"]},{"url":"https://bugzilla.suse.com/1288592","tags":["report"]},{"url":"https://bugzilla.suse.com/1288627","tags":["report"]},{"url":"https://bugzilla.suse.com/1288629","tags":["report"]},{"url":"https://bugzilla.suse.com/1288668","tags":["report"]},{"url":"https://bugzilla.suse.com/1288694","tags":["report"]},{"url":"https://bugzilla.suse.com/1288752","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89626","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92522","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99150","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20265091-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1267882","tags":["report"]},{"url":"https://bugzilla.suse.com/1269182","tags":["report"]},{"url":"https://bugzilla.suse.com/1274257","tags":["report"]},{"url":"https://bugzilla.suse.com/1275521","tags":["report"]},{"url":"https://bugzilla.suse.com/1275955","tags":["report"]},{"url":"https://bugzilla.suse.com/1276245","tags":["report"]},{"url":"https://bugzilla.suse.com/1276275","tags":["report"]},{"url":"https://bugzilla.suse.com/1276440","tags":["report"]},{"url":"https://bugzilla.suse.com/1276443","tags":["report"]},{"url":"https://bugzilla.suse.com/1276774","tags":["report"]},{"url":"https://bugzilla.suse.com/1277079","tags":["report"]},{"url":"https://bugzilla.suse.com/1277084","tags":["report"]},{"url":"https://bugzilla.suse.com/1277130","tags":["report"]},{"url":"https://bugzilla.suse.com/1277135","tags":["report"]},{"url":"https://bugzilla.suse.com/1277142","tags":["report"]},{"url":"https://bugzilla.suse.com/1277157","tags":["report"]},{"url":"https://bugzilla.suse.com/1277168","tags":["report"]},{"url":"https://bugzilla.suse.com/1277182","tags":["report"]},{"url":"https://bugzilla.suse.com/1277200","tags":["report"]},{"url":"https://bugzilla.suse.com/1277333","tags":["report"]},{"url":"https://bugzilla.suse.com/1277451","tags":["report"]},{"url":"https://bugzilla.suse.com/1277675","tags":["report"]},{"url":"https://bugzilla.suse.com/1277732","tags":["report"]},{"url":"https://bugzilla.suse.com/1277785","tags":["report"]},{"url":"https://bugzilla.suse.com/1277819","tags":["report"]},{"url":"https://bugzilla.suse.com/1278074","tags":["report"]},{"url":"https://bugzilla.suse.com/1278081","tags":["report"]},{"url":"https://bugzilla.suse.com/1278117","tags":["report"]},{"url":"https://bugzilla.suse.com/1278172","tags":["report"]},{"url":"https://bugzilla.suse.com/1278198","tags":["report"]},{"url":"https://bugzilla.suse.com/1278213","tags":["report"]},{"url":"https://bugzilla.suse.com/1278217","tags":["report"]},{"url":"https://bugzilla.suse.com/1278350","tags":["report"]},{"url":"https://bugzilla.suse.com/1278379","tags":["report"]},{"url":"https://bugzilla.suse.com/1278405","tags":["report"]},{"url":"https://bugzilla.suse.com/1279420","tags":["report"]},{"url":"https://bugzilla.suse.com/1279460","tags":["report"]},{"url":"https://bugzilla.suse.com/1279700","tags":["report"]},{"url":"https://bugzilla.suse.com/1279823","tags":["report"]},{"url":"https://bugzilla.suse.com/1280312","tags":["report"]},{"url":"https://bugzilla.suse.com/1280330","tags":["report"]},{"url":"https://bugzilla.suse.com/1280331","tags":["report"]},{"url":"https://bugzilla.suse.com/1280332","tags":["report"]},{"url":"https://bugzilla.suse.com/1280346","tags":["report"]},{"url":"https://bugzilla.suse.com/1280988","tags":["report"]},{"url":"https://bugzilla.suse.com/1281006","tags":["report"]},{"url":"https://bugzilla.suse.com/1281080","tags":["report"]},{"url":"https://bugzilla.suse.com/1281145","tags":["report"]},{"url":"https://bugzilla.suse.com/1281256","tags":["report"]},{"url":"https://bugzilla.suse.com/1281274","tags":["report"]},{"url":"https://bugzilla.suse.com/1281342","tags":["report"]},{"url":"https://bugzilla.suse.com/1281528","tags":["report"]},{"url":"https://bugzilla.suse.com/1281532","tags":["report"]},{"url":"https://bugzilla.suse.com/1281536","tags":["report"]},{"url":"https://bugzilla.suse.com/1281552","tags":["report"]},{"url":"https://bugzilla.suse.com/1281555","tags":["report"]},{"url":"https://bugzilla.suse.com/1281588","tags":["report"]},{"url":"https://bugzilla.suse.com/1281883","tags":["report"]},{"url":"https://bugzilla.suse.com/1282165","tags":["report"]},{"url":"https://bugzilla.suse.com/1282169","tags":["report"]},{"url":"https://bugzilla.suse.com/1282735","tags":["report"]},{"url":"https://bugzilla.suse.com/1282741","tags":["report"]},{"url":"https://bugzilla.suse.com/1282886","tags":["report"]},{"url":"https://bugzilla.suse.com/1282958","tags":["report"]},{"url":"https://bugzilla.suse.com/1282971","tags":["report"]},{"url":"https://bugzilla.suse.com/1282993","tags":["report"]},{"url":"https://bugzilla.suse.com/1283038","tags":["report"]},{"url":"https://bugzilla.suse.com/1283173","tags":["report"]},{"url":"https://bugzilla.suse.com/1283228","tags":["report"]},{"url":"https://bugzilla.suse.com/1283233","tags":["report"]},{"url":"https://bugzilla.suse.com/1283504","tags":["report"]},{"url":"https://bugzilla.suse.com/1283508","tags":["report"]},{"url":"https://bugzilla.suse.com/1283513","tags":["report"]},{"url":"https://bugzilla.suse.com/1283737","tags":["report"]},{"url":"https://bugzilla.suse.com/1283780","tags":["report"]},{"url":"https://bugzilla.suse.com/1283781","tags":["report"]},{"url":"https://bugzilla.suse.com/1283785","tags":["report"]},{"url":"https://bugzilla.suse.com/1283887","tags":["report"]},{"url":"https://bugzilla.suse.com/1284303","tags":["report"]},{"url":"https://bugzilla.suse.com/1284306","tags":["report"]},{"url":"https://bugzilla.suse.com/1284561","tags":["report"]},{"url":"https://bugzilla.suse.com/1284600","tags":["report"]},{"url":"https://bugzilla.suse.com/1284632","tags":["report"]},{"url":"https://bugzilla.suse.com/1284642","tags":["report"]},{"url":"https://bugzilla.suse.com/1285594","tags":["report"]},{"url":"https://bugzilla.suse.com/1285645","tags":["report"]},{"url":"https://bugzilla.suse.com/1285647","tags":["report"]},{"url":"https://bugzilla.suse.com/1286001","tags":["report"]},{"url":"https://bugzilla.suse.com/1286133","tags":["report"]},{"url":"https://bugzilla.suse.com/1286186","tags":["report"]},{"url":"https://bugzilla.suse.com/1286208","tags":["report"]},{"url":"https://bugzilla.suse.com/1286458","tags":["report"]},{"url":"https://bugzilla.suse.com/1286665","tags":["report"]},{"url":"https://bugzilla.suse.com/1286667","tags":["report"]},{"url":"https://bugzilla.suse.com/1286670","tags":["report"]},{"url":"https://bugzilla.suse.com/1286673","tags":["report"]},{"url":"https://bugzilla.suse.com/1286674","tags":["report"]},{"url":"https://bugzilla.suse.com/1286694","tags":["report"]},{"url":"https://bugzilla.suse.com/1286708","tags":["report"]},{"url":"https://bugzilla.suse.com/1286744","tags":["report"]},{"url":"https://bugzilla.suse.com/1286826","tags":["report"]},{"url":"https://bugzilla.suse.com/1286870","tags":["report"]},{"url":"https://bugzilla.suse.com/1287647","tags":["report"]},{"url":"https://bugzilla.suse.com/1287981","tags":["report"]},{"url":"https://bugzilla.suse.com/1288126","tags":["report"]},{"url":"https://bugzilla.suse.com/1288226","tags":["report"]},{"url":"https://bugzilla.suse.com/1288406","tags":["report"]},{"url":"https://bugzilla.suse.com/1288513","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98522","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99094","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-74715","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74715","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8886-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8959-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8960-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-37807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-68479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-72502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74517","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-74754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-80999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-81018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89654","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89690","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89717","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89837","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-89999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-90435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92517","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-92525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-93830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97517","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97600","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-97998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98435","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98479","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98486","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98517","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98536","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98541","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98547","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98558","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98559","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98564","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98567","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98573","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98592","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98621","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98631","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98647","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98888","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98896","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98906","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-98930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-100079","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-74715","title":"bpf: Fix netns reference imbalance in conntrack kfuncs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T15:33:10.262Z","modified":"2026-10-30T12:30:22.773Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:20:03.081354Z"}],"euvd":[{"id":"EUVD-2026-64402","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T15:33:10Z","modified":"2026-10-30T12:30: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"}],"updated_at":"2026-11-02T16:59:09.83103Z"}],"ghsa":[{"id":"GHSA-8qqv-vcf6-q7hx","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T18:30:30Z","modified":"2026-10-30T15:34:14Z","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:14:48.577424Z"}],"nvd":[{"id":"CVE-2026-74715","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T16:16:46.313Z","modified":"2026-10-30T13:20:04.647Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"}],"updated_at":"2026-11-02T14:12:40.665005Z"}],"osv":[{"id":"BELL-CVE-2026-74715","status":"published","published":"2026-08-27T06:10:32.566523Z","modified":"2026-11-04T07:16:16.01580825Z","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-04T07:31:37.974902Z"},{"id":"CVE-2026-74715","title":"bpf: Fix netns reference imbalance in conntrack kfuncs","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T15:33:10.262Z","modified":"2026-11-06T17:27:27.196157723Z","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-06T18:02:03.661987Z"},{"id":"DEBIAN-CVE-2026-74715","description":"In the Linux kernel, the following vulnerability has been resolved:  bpf: Fix netns reference imbalance in conntrack kfuncs  The opts argument of the BPF conntrack kfuncs can point to a shared map value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read opts-\u003enetns_id separately when acquiring and releasing the network namespace reference.  The reference imbalance can occur as follows:    CPU 0                                  CPU 1   read opts-\u003enetns_id (-1)   skip get_net_ns_by_id()                                          write opts-\u003enetns_id (id)   read opts-\u003enetns_id (id)   put_net(net) /* no matching get */  The reverse transition leaks the reference.  Repeating the unmatched put can destroy a live namespace and crash later users.  The kernel reported:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]   RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700   Call Trace:    __sys_bpf+0x1662/0x50c0    __x64_sys_bpf+0x73/0xb0    do_syscall_64+0xf9/0x540    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception  Snapshot every input field of opts with READ_ONCE() before validating or using it.  The netns_id snapshot keeps the namespace get/put pair balanced, while the other snapshots keep the remaining options from changing partway through an invocation.  The individual reads can still observe an inconsistent combination during a concurrent update, but each selected field value remains stable for that invocation.","status":"published","published":"2026-08-22T16:16:46.313Z","modified":"2026-11-02T18:00:44.717159328Z","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-02T19:03:20.122208Z"},{"id":"OESA-2026-3707","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\nseg6: separate dst_cache for input and output paths in seg6 lwtunnel\n\nThe seg6 lwtunnel uses a single dst_cache per encap route, shared\nbetween seg6_input_core() and seg6_output_core(). These two paths\ncan perform the post-encap SID lookup in different routing contexts\n(e.g., ip rules matching on the ingress interface, or VRF table\nseparation). Whichever path runs first populates the cache, and the\nother reuses it blindly, bypassing its own lookup.\n\nFix this by splitting the cache into cache_input and cache_output,\nso each path maintains its own cached dst independently.(CVE-2026-31668)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix iova-to-va conversion for MR page sizes != PAGE_SIZE\n\nThe current implementation incorrectly handles memory regions (MRs) with\npage sizes different from the system PAGE_SIZE. The core issue is that\nrxe_set_page() is called with mr-\u0026gt;page_size step increments, but the\npage_list stores individual struct page pointers, each representing\nPAGE_SIZE of memory.\n\nib_sg_to_page() has ensured that when i\u0026gt;=1 either\na) SG[i-1].dma_end and SG[i].dma_addr are contiguous\nor\nb) SG[i-1].dma_end and SG[i].dma_addr are mr-\u0026gt;page_size aligned.\n\nThis leads to incorrect iova-to-va conversion in scenarios:\n\n1) page_size \u0026lt; PAGE_SIZE (e.g., MR: 4K, system: 64K):\n   ibmr-\u0026gt;iova = 0x181800\n   sg[0]: dma_addr=0x181800, len=0x800\n   sg[1]: dma_addr=0x173000, len=0x1000\n\n   Access iova = 0x181800 + 0x810 = 0x182010\n   Expected VA: 0x173010 (second SG, offset 0x10)\n   Before fix:\n     - index = (0x182010 \u0026gt;\u0026gt; 12) - (0x181800 \u0026gt;\u0026gt; 12) = 1\n     - page_offset = 0x182010 \u0026amp; 0xFFF = 0x10\n     - xarray[1] stores system page base 0x170000\n     - Resulting VA: 0x170000 + 0x10 = 0x170010 (wrong)\n\n2) page_size \u0026gt; PAGE_SIZE (e.g., MR: 64K, system: 4K):\n   ibmr-\u0026gt;iova = 0x18f800\n   sg[0]: dma_addr=0x18f800, len=0x800\n   sg[1]: dma_addr=0x170000, len=0x1000\n\n   Access iova = 0x18f800 + 0x810 = 0x190010\n   Expected VA: 0x170010 (second SG, offset 0x10)\n   Before fix:\n     - index = (0x190010 \u0026gt;\u0026gt; 16) - (0x18f800 \u0026gt;\u0026gt; 16) = 1\n     - page_offset = 0x190010 \u0026amp; 0xFFFF = 0x10\n     - xarray[1] stores system page for dma_addr 0x170000\n     - Resulting VA: system page of 0x170000 + 0x10 = 0x170010 (wrong)\n\nYi Zhang reported a kernel panic[1] years ago related to this defect.\n\nSolution:\n1. Replace xarray with pre-allocated rxe_mr_page array for sequential\n   indexing (all MR page indices are contiguous)\n2. Each rxe_mr_page stores both struct page* and offset within the\n   system page\n3. Handle MR page_size != PAGE_SIZE relationships:\n   - page_size \u0026gt; PAGE_SIZE: Split MR pages into multiple system pages\n   - page_size \u0026lt;= PAGE_SIZE: Store offset within system page\n4. Add boundary checks and compatibility validation\n\nThis ensures correct iova-to-va conversion regardless of MR page size\nand system PAGE_SIZE relationship, while improving performance through\narray-based sequential access.\n\nTests on 4K and 64K PAGE_SIZE hosts:\n- rdma-core/pytests\n  $ ./build/bin/run_tests.py  --dev eth0_rxe\n- blktest:\n  $ TIMEOUT=30 QUICK_RUN=1 USE_RXE=1 NVMET_TRTYPES=rdma ./check nvme srp rnbd\n\n[1] https://lore.kernel.org/all/CAHj4cs9XRqE25jyVw9rj9YugffLn5+f=1znaBEnu1usLOciD+g@mail.gmail.com/T/(CVE-2026-46325)\n\nIn the Linux kernel, compat_riscv_gpr_set() calls cregs_to_regs() unconditionally, even when user_regset_copyin() fails. Since cregs is an uninitialized stack variable, a copyin failure causes uninitialized stack data to be written into the target task\u0026apos;s pt_regs, corrupting its register state and potentially leaking kernel stack contents. compat_restore_sigcontext() has the same issue: it calls cregs_to_regs() even when __copy_from_user() fails, leading to the same corruption of the signal-returning task\u0026apos;s register state on error.(CVE-2026-64082)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_conn: Fix null ptr deref in hci_abort_conn()\n\nhci_abort_conn() read hci_skb_event(hdev-\u0026gt;sent_cmd) when a connection\nwas pending, but hdev-\u0026gt;sent_cmd can be NULL while req_status is still\nHCI_REQ_PEND, leading to a NULL pointer dereference and a general\nprotection fault from the hci_rx_work() receive path.\n\nInstead of inspecting hdev-\u0026gt;sent_cmd, track the in-flight create\nconnection command with a new per-connection HCI_CONN_CREATE flag and\nroute all cancellation through hci_cancel_connect_sync(), which\ndispatches to a dedicated per-type cancel function. The create command\nis in exactly one of two states: still queued, or in flight. The cancel\nfunction holds cmd_sync_work_lock across the whole decision: the worker\ntakes this lock to dequeue every entry, so while it is held a queued\ncommand cannot start running and an in-flight command cannot complete\nand let the next command become pending. This keeps the flag test and\nhci_cmd_sync_cancel() atomic with respect to the worker, so a queued\ncommand is simply dequeued, and an in-flight command owned by this\nconnection is cancelled without the risk of cancelling an unrelated\ncommand that became pending in the meantime. CIS uses the same flag\nmechanism via HCI_CONN_CREATE_CIS but cannot be dequeued per-connection.\n\nhci_acl_create_conn_sync() and hci_le_create_conn_sync() clear\nHCI_CONN_CREATE after the create command completes, but the command\nstatus handler can free conn via hci_conn_del() (for example when the\ncontroller rejects the connection) while the worker is still blocked on\nthe connection complete event. Hold a reference on conn across the\ncreate command so the flag can be cleared without a use-after-free.(CVE-2026-64405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/handshake: Take a long-lived file reference at submit\n\nhandshake_nl_accept_doit() needs the file pointer backing\nreq-\u0026gt;hr_sk-\u0026gt;sk_socket to survive the window between\nhandshake_req_next() and the subsequent FD_PREPARE() and get_file().\nThe submit-side sock_hold() does not provide that.  sk_refcnt keeps\nstruct sock alive, but struct socket is owned by sock-\u0026gt;file: when\nthe consumer fputs the last file reference, sock_release() tears\nthe socket down regardless of any sock_hold.\n\nAdd an hr_file pointer to struct handshake_req and acquire an\nexplicit reference on sock-\u0026gt;file during handshake_req_submit().\nhandshake_complete() and handshake_req_cancel() release the\nreference on the completion-bit-winning path.\n\nThe submit error path must also release the file reference, but\nafter rhashtable insertion a concurrent handshake_req_cancel() can\ndiscover the request and race the error path.  Gate the error-path\ncleanup -- sk_destruct restoration, fput, and request destruction\n-- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same\nserialization handshake_complete() and handshake_req_cancel()\nalready use.  When cancel has already claimed ownership, the submit\nerror path returns without touching the request; socket teardown\nhandles final destruction.\n\nThe accept-side dereferences are not yet retargeted; that change\ncomes in the next patch.(CVE-2026-64523)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix two unsafe bare decodes in decode_lockers()\n\ndecode_lockers() in cls_lock_client.c contains two bare decode operations\nthat allow a malicious or compromised OSD to trigger slab-out-of-bounds\nreads:\n\n1. ceph_decode_32(p) at the num_lockers field has no preceding bounds\n   check. ceph_start_decoding() accepts struct_len=0 as valid -- the\n   internal ceph_decode_need(p, end, 0, bad) always passes -- so when an\n   OSD sends struct_len=0, ceph_start_decoding() returns success with\n   p == end. The immediately following bare ceph_decode_32(p) then reads\n   4 bytes past the validated buffer boundary. The garbage value is\n   passed directly to kzalloc_objs() as the locker count.\n\n   The sibling function decode_watchers() in osd_client.c already uses\n   ceph_decode_32_safe() after its own ceph_start_decoding() call.\n   decode_lockers() was the only site using the bare variant.\n\n2. ceph_decode_8(p) after the decode_locker() loop has no preceding\n   bounds check. If an OSD crafts num_lockers such that the loop\n   advances p exactly to end, the subsequent bare ceph_decode_8(p) reads\n   one byte past the validated buffer boundary. The result is passed\n   directly into *type, which is used as a lock type discriminator by\n   callers, giving an OSD-controlled one-byte OOB read with direct\n   influence over the lock type field.\n\nFix both by replacing bare operations with their safe variants:\n  ceph_decode_32(p) -\u0026gt; ceph_decode_32_safe(p, end, *num_lockers,\n                                           err_inval)\n  ceph_decode_8(p)  -\u0026gt; ceph_decode_8_safe(p, end, *type,\n                                          err_free_lockers)\n\nThe goto targets differ intentionally:\n  err_inval: is a new label returning -EINVAL directly. It is used for\n  the pre-allocation failure path where *lockers is not yet allocated\n  and must not be passed to ceph_free_lockers().\n\n  err_free_lockers: is the existing label. It is used for the\n  post-allocation failure path where *lockers is allocated and must\n  be freed.\n\nret is set to -EINVAL before ceph_decode_8_safe() so that\nerr_free_lockers returns the correct error code on bounds violation.\nWithout this, err_free_lockers would return a stale ret value (0 from\nthe successful decode_locker() loop), silently swallowing the error.\n\n-EINVAL is correct for both failure paths. The data received from the\nOSD is structurally malformed. -ENOMEM would misrepresent the failure\nclass to callers and to stable@ backporters triaging error paths.\n\nAttacker model: a malicious or compromised OSD in a multi-tenant Ceph\ndeployment can trigger this against any kernel client that issues the\nlock.get_info class method (e.g. during RBD exclusive lock acquisition).\n\n[ idryomov: trim changelog, formatting ](CVE-2026-68082)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: challenge ACK for non-exact RST in SYN-RECEIVED\n\nThe SYN-RECEIVED request-socket path in tcp_check_req() accepts an\nin-window RST without requiring SEG.SEQ to exactly match RCV.NXT.  A\nnon-exact RST therefore removes the request instead of eliciting a\nchallenge ACK.\n\nRFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in\nSYN-RECEIVED: an exact RST resets the connection, while a non-exact\nin-window RST must trigger a challenge ACK and be dropped.\n\nApply that check before the ACK-field validation, following the RFC\nsequence-number, RST, then ACK processing order.  Factor the per-netns\nchallenge ACK quota out of tcp_send_challenge_ack() so request sockets\ncan share it.  Use the request socket\u0026apos;s send_ack() callback and its own\nout-of-window ACK timestamp to send and rate-limit the response.(CVE-2026-68118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: fix double aggregation of flush-marked skbs\n\nCommit 0ab03f353d36 (\u0026quot;net-gro: Fix GRO flush when receiving a GSO\npacket.\u0026quot;) added a flush check to skb_gro_receive(), but\nskb_gro_receive_list() lacks the same validation.\n\nAs a result, packets marked with NAPI_GRO_CB(skb)-\u0026gt;flush may still be\nre-aggregated.\n\nThis allows already-GRO\u0026apos;d packets with existing frag_list to be\nre-aggregated into a new GRO session, corrupting the frag_list chain\nstructure. When skb_segment() attempts to unpack these malformed packets,\nit encounters invalid state and triggers a kernel panic.\n\nScenario (Tethering/Device forwarding):\n  1. Driver: Generated aggregated packet P1 via LRO with frag_list\n  2. Dev A: Receives aggregated fraglist packet and flush flag set\n  3. Dev A: Re-enters GRO, skb_gro_receive_list() is called\n  4. Missing flush check allows re-aggregation despite flush flag\n  5. Frag_list chain becomes corrupted (loops or dangling refs)\n  6. Dev B: TX path calls skb_segment(), crashes on corrupted frag_list\n\nRoot cause in skb_segment():\n  The check at line ~4891:\n    if (hsize \u0026lt;= 0 \u0026amp;\u0026amp; i \u0026gt;= nfrags \u0026amp;\u0026amp; skb_headlen(list_skb) \u0026amp;\u0026amp;\n        (skb_headlen(list_skb) == len || sg)) {\n\n  When frag_list is corrupted by double aggregation, when list_skb is\n  a NULL pointer from skb-\u0026gt;next, skb_headlen(list_skb) dereference\n  NULL/corrupted pointers occurs.\n\nCall Trace:\n skb_headlen(NULL skb)\n skb_segment\n tcp_gso_segment\n tcp4_gso_segment\n inet_gso_segment\n skb_mac_gso_segment\n __skb_gso_segment\n skb_gso_segment\n validate_xmit_skb\n validate_xmit_skb_list\n sch_direct_xmit\n qdisc_restart\n __qdisc_run\n qdisc_run\n net_tx_action\n\nFix: Add NAPI_GRO_CB(skb)-\u0026gt;flush validation to the early-return check in\nskb_gro_receive_list(), matching the defensive programming pattern of\nskb_gro_receive().(CVE-2026-68136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: serialize qdisc_rtab_list against concurrent get/put\n\nqdisc_get_rtab() and qdisc_put_rtab() mutate the process-global singly\nlinked list qdisc_rtab_list and a plain non-atomic \u0026apos;int refcnt\u0026apos; with no\nlock. This was only safe because every caller historically held the RTNL\nmutex, which serialized all rate-table lookups, inserts and frees.\n\nThat invariant no longer holds. cls_flower sets\nTCF_PROTO_OPS_DOIT_UNLOCKED, so tc_new_tfilter() keeps rtnl_held == false\nfor it and sets TCA_ACT_FLAGS_NO_RTNL. That flag propagates through\ntcf_exts_validate_ex() -\u0026gt; tcf_action_init() -\u0026gt; tcf_action_init_1() -\u0026gt;\ntcf_police_init(), which calls qdisc_get_rtab()/qdisc_put_rtab() with the\nRTNL mutex NOT held. Two RTM_NEWTFILTER requests on different CPUs, each\nadding a flower filter with a police action carrying the same rate, then\nrace on qdisc_rtab_list and on the non-atomic refcnt, leading to a\nuse-after-free / double-free of the kmalloc-2k struct qdisc_rate_table.\nqdisc_rtab_list is a single global (not per-netns), so the corrupted\nobject is shared system-wide.\n\n  BUG: KASAN: slab-use-after-free in qdisc_put_rtab+0x12f/0x160\n   qdisc_put_rtab+0x12f/0x160\n   tcf_police_init+0xda9/0x1590\n   tcf_action_init_1+0x460/0x6b0\n   tcf_action_init+0x439/0xa40\n   tcf_exts_validate_ex+0x42d/0x550\n   fl_change+0xddd/0x7da0\n   tc_new_tfilter+0xaa7/0x2420\n   rtnetlink_rcv_msg+0x95e/0xe90\n  which belongs to the cache kmalloc-2k of size 2048\n\nProtect qdisc_rtab_list and the refcount with a dedicated spinlock. The\n(sleeping, GFP_KERNEL) allocation in qdisc_get_rtab() is performed before\ntaking the lock; if a concurrent inserter added an identical table in the\nmeantime the freshly allocated one is freed under the lock, so no\nduplicate is leaked. qdisc_put_rtab() now decrements the refcount and\nunlinks under the same lock.(CVE-2026-68138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: fix out-of-bounds bitmap_set() with zero-length range\n\nifs_set_range_dirty() and ifs_set_range_uptodate() compute last_blk\nas (off + len - 1) \u0026gt;\u0026gt; i_blkbits.  When off is 0 and len is 0, the\nunsigned subtraction underflows to SIZE_MAX, producing a huge\nlast_blk and nr_blks value that causes bitmap_set() to write far\nbeyond the ifs-\u0026gt;state allocation.\n\nRegarding ifs_set_range_uptodate(), it is temporarily safe because len\ncannot be passed in as 0. However, for ifs_set_range_dirty() this is\nreachable from __iomap_write_end(): when copy_folio_from_iter_atomic()\nreturns 0 (e.g. user buffer fault) and the folio is already uptodate,\nthe guard at the top of __iomap_write_end() does not trigger because\n!folio_test_uptodate() is false, and iomap_set_range_dirty() is called\nwith copied == 0.\n\nAdd a !len guard to both functions before the computation, so that a\nzero-length range is a no-op.(CVE-2026-68145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE\n\n__decode_pg_temp() decodes an user-controlled length but only rejects\nvalues large enough to overflow the allocation; it does not bound it to\nCEPH_PG_MAX_SIZE. The helper backs both pg_temp and pg_upmap decoding, and\napply_upmap()/get_temp_osds() later copy the decoded list into the fixed-size\non-stack array struct ceph_osds.osds[CEPH_PG_MAX_SIZE]. A monitor that sends\nan OSDMap with a pg_temp/pg_upmap entry longer than 32 thus causes a stack\nout-of-bounds write.\n\nAn OSD set for a single PG can never exceed CEPH_PG_MAX_SIZE, so reject longer\nentries at decode time. The bound is well below the old overflow threshold, so\nit also covers the allocation-size overflow the previous check guarded against.\n\n  BUG: KASAN: stack-out-of-bounds in ceph_pg_to_up_acting_osds\n  Write of size 4 ... by task exploit\n   kasan_report (mm/kasan/report.c:595)\n   ceph_pg_to_up_acting_osds (net/ceph/osdmap.c:2617 net/ceph/osdmap.c:2833)\n   calc_target (net/ceph/osd_client.c:1638)\n   __submit_request (net/ceph/osd_client.c:2394)\n   ceph_osdc_start_request (net/ceph/osd_client.c:2490)\n   ceph_osdc_call (net/ceph/osd_client.c:5164)\n   rbd_dev_image_probe (drivers/block/rbd.c:6899)\n   do_rbd_add (drivers/block/rbd.c:7138)\n   ...\n  kernel BUG at net/ceph/osdmap.c:2670!\n\n[ idryomov: do the same in __decode_pg_upmap_items() ](CVE-2026-68159)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor()\n\nThe v4l2 helper v4l2_async_register_subdev_sensor() calls\nv4l2_async_register_subdev(), which is a macro that expands to\n__v4l2_async_register_subdev(sd,THIS_MODULE). Since the macro is expanded\ninside v4l2-fwnode.c, THIS_MODULE resolves to the v4l2-fwnode module\nrather than the sensor driver module that originally set sd-\u0026gt;owner. When\nv4l2-fwnode is built-in, THIS_MODULE evaluates to NULL, which then\noverwrites the sensor driver\u0026apos;s owner with NULL.\n\nThis causes the problem that the sensor module\u0026apos;s reference count is never\nincremented during async registration, so the module can be removed while\nthe subdevice is still in use by a notifier (e.g., a CSI-2 receiver\nbridge driver).\n\nFix this by renaming v4l2_async_register_subdev_sensor() to\n__v4l2_async_register_subdev_sensor() with an added explicit module\nargument and introducing a wrapper macro:\n    #define v4l2_async_register_subdev_sensor(sd) \\\n        __v4l2_async_register_subdev_sensor(sd, THIS_MODULE)\n\nThis ensures the sensor driver module is properly referenced even when\nthe sensor driver does not init the owner field before calling\nv4l2_async_register_subdev_sensor() and prevents premature module removal.(CVE-2026-68205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: fix stale skb-\u0026gt;prev after async crypto steals a GSO segment\n\nskb_gso_segment() leaves the segment list head with -\u0026gt;prev pointing at\nthe last segment, an invariant validate_xmit_skb_list() relies on when\nit sets its tail pointer (tail = skb-\u0026gt;prev).\n\nWhen validate_xmit_xfrm() walks a GSO list and some segments are stolen\nby async crypto (-\u0026gt;xmit() returns -EINPROGRESS), those segments are\nunlinked from the list but the head -\u0026gt;prev is never updated.  If the\nlast segment is the one stolen, the returned head still has -\u0026gt;prev\npointing at it, even though it is now owned by the crypto engine and may\nbe freed.  validate_xmit_skb_list() later does tail-\u0026gt;next = skb, writing\nthrough that stale pointer -- a use-after-free.\n\nRepoint skb-\u0026gt;prev at the last retained segment before returning.(CVE-2026-68426)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ieee80211: validate MLE common info length\n\nieee80211_mle_common_size() uses the first common-info octet as the\ncommon information length for all known MLE types. However,\nieee80211_mle_size_ok() only validates that octet for Basic, Probe\nRequest, and TDLS MLEs.\n\nReconfiguration MLEs also skipped the length octet when calculating the\nminimum common size, and Priority Access MLEs skipped validation of the\nadvertised common information length.\n\nAccount for the Reconfiguration common-info length octet and validate\nthe advertised common information length for all known MLE types. Keep\nunknown-type handling unchanged.\n\n[remove now misleading comment](CVE-2026-68471)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm-verity: fix buffer overflow in FEC calculation\n\nThere\u0026apos;s a buffer overflow in dm-verity-fec:\n\nif (neras \u0026amp;\u0026amp; *neras \u0026lt;= v-\u0026gt;fec-\u0026gt;roots)\n\tfio-\u0026gt;erasures[(*neras)++] = i;\n\nThis allows *neras to reach roots + 1 (the post-increment pushes it past\nroots). This value is then passed as no_eras to decode_rs8(). Inside the\nRS decoder (lib/reed_solomon/decode_rs.c:113-121), the erasure locator\npolynomial loop writes lambda[j] where j can reach nroots + 1 — one\nelement past the end of lambda[] (which is sized nroots + 1, valid\nindices 0..nroots). The out-of-bounds write lands on syn[0], corrupting\nthe syndrome buffer.(CVE-2026-72098)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reset register bounds before narrowing retval range in check_mem_access()\n\nWhen the BPF verifier processes a context load of an LSM hook return\nvalue, it calls __mark_reg_s32_range() to narrow the register to the\nhook\u0026apos;s valid range. However, __mark_reg_s32_range() intersects the new\nrange with the register\u0026apos;s existing bounds using max_t()/min_t() rather\nthan replacing them.\n\nIf the destination register carries stale bounds from a prior instruction\n(e.g. BPF_MOV64_IMM), the intersection can produce a range narrower than\nreality. The verifier then believes it knows the register\u0026apos;s exact value,\nwhile at runtime the actual hook return value is loaded, creating a\nverifier/runtime mismatch that can be used to bypass BPF memory safety\nchecks.\n\nThe else branch already calls mark_reg_unknown() to reset register state\nbefore any narrowing. Apply the same reset in the is_retval path so\nstale bounds are cleared before __mark_reg_s32_range() intersects.(CVE-2026-72111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch\n\nIn alloc_hugetlb_folio(), a single h_cg pointer is used for both the rsvd\nand non-rsvd hugetlb cgroup charges.  When map_chg is set,\nhugetlb_cgroup_charge_cgroup_rsvd() stores the charged cgroup in h_cg, but\nthe immediately following hugetlb_cgroup_charge_cgroup() overwrites h_cg\nwith the non-rsvd cgroup pointer.\n\nAs a result, hugetlb_cgroup_commit_charge_rsvd() stores the wrong\n(non-rsvd) cgroup pointer into the folio\u0026apos;s rsvd slot.\n\nWhen the folio is later freed, free_huge_folio() unconditionally calls\nboth hugetlb_cgroup_uncharge_folio() and\nhugetlb_cgroup_uncharge_folio_rsvd().  The rsvd uncharge reads back the\nwrong cgroup from the folio and decrements a counter that was never\ncharged for that cgroup, causing a page_counter underflow:\n\n  page_counter underflow: -512 nr_pages=512\n  WARNING: mm/page_counter.c:61 at page_counter_cancel\n\nFix this by introducing a separate h_cg_rsvd pointer exclusively for the\nrsvd charge path, keeping the rsvd and non-rsvd charges fully independent\nthrough their charge, commit, and error uncharge paths.(CVE-2026-72213)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: fix zone comparison in tuple dedup\n\nThe \u0026quot;already exists\u0026quot; dedup logic in __nf_conncount_add() decides\nwhether a connection has already been counted and can be skipped instead\nof incrementing the connlimit count.  It compares the conntrack zone of a\nlist entry with the zone of the connection being added using\nnf_ct_zone_id() and nf_ct_zone_equal(), passing conn-\u0026gt;zone.dir or\nzone-\u0026gt;dir as the direction argument.\n\nThose helpers take enum ip_conntrack_dir values: IP_CT_DIR_ORIGINAL is 0\nand IP_CT_DIR_REPLY is 1.  However, zone-\u0026gt;dir is a u8 bitmask:\nNF_CT_ZONE_DIR_ORIG is 1, NF_CT_ZONE_DIR_REPL is 2 and\nNF_CT_DEFAULT_ZONE_DIR is 3.  Passing that bitmask as the enum direction\nshifts the meaning of every non-zero value.  An ORIG-only zone passes 1\nand is tested as REPLY, while REPL-only and default zones pass 2 or 3 and\ntest bits beyond the valid direction range.  In those cases\nnf_ct_zone_id() can fall back to NF_CT_DEFAULT_ZONE_ID instead of using\nthe real zone id, so different zones can be treated as equal and dedup\ncollapses to tuple equality alone.\n\nnf_conncount stores and compares the original-direction tuple for a\nconnection.  If an skb already has an attached conntrack entry,\nget_ct_or_tuple_from_skb() explicitly copies\nct-\u0026gt;tuplehash[IP_CT_DIR_ORIGINAL].tuple, regardless of the packet\u0026apos;s\nctinfo.  Therefore the zone comparison in the tuple dedup path must use\nIP_CT_DIR_ORIGINAL as well; the zone direction bitmask describes where a\nzone id applies, not which direction this conncount tuple represents.\n\nFix the two dedup comparisons by passing IP_CT_DIR_ORIGINAL directly.\nDo not special-case NF_CT_DEFAULT_ZONE_DIR and do not compare raw zone\nids: using the existing helpers with IP_CT_DIR_ORIGINAL preserves the\ndirection-aware NF_CT_DEFAULT_ZONE_ID fallback.  A default bidirectional\nzone contains the ORIG bit, so it naturally returns the real zone id;\nreply-only zones continue to fall back for original-direction tuple\ncomparisons.(CVE-2026-72247)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling\n\nHyunwoo Kim reports some really bad races should the following\nsituation occur:\n\n- LPI-I is pending in vcpu-B\u0026apos;s AP list\n- vcpu-A writes to vcpu-B\u0026apos;s RD to disable its LPIs\n- vcpu-C moves I from B to C\n\nIf the last two race nicely enough, vgic_prune_ap_list() can drop\nthe irq and AP list locks, reacquire them, and in the interval\nthe irq has been freed. UAF follows.\n\nThe fix is two-fold:\n\n- Before dropping the irq and ap_list locks, take a reference on\n  the irq\n\n- Do not try to handle migration of the pending bit: there is no\n  expectation that this state is retained, as per the architecture\n\nWith that, we\u0026apos;re sure that the interrupt is still around, and we\nsafely remove it from the AP list as it has no target at this\nstage (unless another interrupt fires, but that\u0026apos;s another story).(CVE-2026-72288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Check irq validity in kvm_vcpu_ioctl_interrupt()\n\nFunction kvm_vcpu_ioctl_interrupt() can be called from userspace, here\nadd irq validility cheking in kvm_vcpu_ioctl_interrupt().(CVE-2026-72294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: igmp: Fix potential memory leaks in igmp_mod_timer() and igmp_stop_timer()\n\nWhen a timer is deleted and not re-armed in igmp_mod_timer(), or stopped\nin igmp_stop_timer(), the code currently decrements the reference counter\nof the multicast list entry @im using refcount_dec(\u0026amp;im-\u0026gt;refcnt).\n\nHowever, both functions can be called from the RCU reader path:\n- igmp_mod_timer() via igmp_heard_query() -\u0026gt; for_each_pmc_rcu()\n- igmp_stop_timer() via igmp_rcv() -\u0026gt; igmp_heard_report()\n\nIf the group im was concurrently removed from the list by ip_mc_dec_group(),\nits reference count might have already been decremented to 1.\n\nIn this case, timer_delete() succeeds, and refcount_dec() decrements\nthe refcount from 1 to 0. Since refcount_dec() does not free the object\nwhen it hits 0 (unlike ip_ma_put()), the im structure is leaked.\n\nFix this by using ip_ma_put(im) instead of refcount_dec(\u0026amp;im-\u0026gt;refcnt),\nand deferring the put until after the spinlock is released.(CVE-2026-72321)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/liquidio: drop cached VF pci_dev LUT\n\nThe PF SR-IOV enable path caches VF pci_dev pointers in\ndpiring_to_vfpcidev_lut[] by iterating with pci_get_device(). Those\nentries do not own a reference, because the iterator drops the previous\ndevice reference on each step. The cached pointer is then dereferenced\nlater when handling OCTEON_VF_FLR_REQUEST.\n\nReplace the cached VF mapping with runtime lookup on the mailbox DPI\nring: derive the VF index from q_no, resolve the VF via exported PCI\nIOV helpers, validate it with the PF pointer and VF ID, then issue\npcie_flr() and drop the reference with pci_dev_put(). Remove the\nunused VF lookup table initialization and cleanup.(CVE-2026-72329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: add INIT verification after cookie unpacking\n\nIn SCTP handshake, the INIT chunk is initially processed by the server\nand embedded into the cookie carried in INIT-ACK. The client then\nreturns this cookie via COOKIE-ECHO, where the server unpacks it and\nreconstructs the original INIT chunk.\n\nWhen cookie authentication is enabled, the cookie contents are protected\nagainst tampering, so reusing the unpacked INIT without re-verification\nis safe.\n\nHowever, when cookie authentication is disabled, the reconstructed INIT\ncan no longer be trusted. In this case, the INIT must be explicitly\nvalidated after unpacking to avoid processing potentially tampered data.\n\nAdd sctp_verify_init() checks after cookie unpacking in COOKIE-ECHO\nprocessing paths (sctp_sf_do_5_1D_ce() and sctp_sf_do_5_2_4_dupcook())\nwhen cookie_auth_enable is disabled. On failure, the new association is\nfreed and the packet is discarded.\n\nAlso tighten cookie validation in sctp_unpack_cookie() by verifying the\nembedded chunk type is SCTP_CID_INIT before treating it as an INIT\nchunk.\n\nFinally, update sctp_verify_init() to validate parameter bounds using\nthe actual embedded INIT length instead of chunk-\u0026gt;chunk_end, since the\nINIT stored in COOKIE-ECHO may not span the entire chunk buffer.(CVE-2026-72398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()\n\nTIPC UDP media bearer teardown calls dst_cache_destroy() on its\nreplicast caches before calling synchronize_net() to wait for\nconcurrent RCU readers (transmitters) to finish:\n\nstatic void cleanup_bearer(struct work_struct *work)\n{\n...\n\tlist_for_each_entry_safe(rcast, tmp, \u0026amp;ub-\u0026gt;rcast.list, list) {\n\t\tdst_cache_destroy(\u0026amp;rcast-\u0026gt;dst_cache);\n\t\tlist_del_rcu(\u0026amp;rcast-\u0026gt;list);\n\t\tkfree_rcu(rcast, rcu);\n\t}\n...\n\tdst_cache_destroy(\u0026amp;ub-\u0026gt;rcast.dst_cache);\n\tudp_tunnel_sock_release(ub-\u0026gt;sk);\n\tsynchronize_net();\n...\n}\n\nThis is highly buggy because dst_cache_destroy() immediately frees the\nper-CPU cache memory (free_percpu()) and releases the cached dst\nentries without any synchronization.\n\nIf a concurrent transmitter (e.g., tipc_udp_xmit()) is running on another\nCPU under RCU protection, it can call dst_cache_get() concurrently,\nleading to:\n1. Use-After-Free on the per-CPU cache pointer itself (crash).\n2. \u0026quot;rcuref - imbalanced put()\u0026quot; warning if it attempts to release a\n   dst that was concurrently released by dst_cache_destroy().\n\nFurthermore, calling kfree(ub) immediately after synchronize_net() without\nclosing the socket first (or waiting after closing it) leaves a window\nwhere a concurrent receiver (tipc_udp_recv()) could start after\nsynchronize_net(), access ub, and suffer a UAF when kfree(ub) runs.\n\nTo fix this, we must defer dst_cache_destroy() and kfree(ub) until after\nwe have ensured that no more readers can see the bearer/socket and all\nexisting readers have finished:\n\n1. Defer rcast entry destruction (both dst_cache_destroy() and kfree())\n   to an RCU callback using call_rcu_hurry().\n   Using call_rcu_hurry() ensures the dst entries are released quickly.\n\n2. Release the bearer socket using udp_tunnel_sock_release() (stops\n   new receive readers).\n\n3. Call synchronize_net() to wait for all outstanding RCU readers\n   (both transmit and receive) to finish.\n\n4. Now that it is safe, call dst_cache_destroy() on the main bearer\n   cache, and free ub.\n\nNote: 3) and 4) can be changed later in net-next to also use\ncall_rcu_hurry() and get rid of the synchronize_net() latency.(CVE-2026-72404)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync\n\nYue Sun reported a use-after-free and debugobjects warning in\nudp_tunnel_nic_device_sync_work() during concurrent device operations.\n\nThe workqueue core clears the internal pending bit before invoking the\nworker. At that point, a concurrent thread can queue the work again.\nWhen the already running worker eventually clears the work_pending flag\nto 0, it mistakenly clears the flag for the newly queued instance.\nudp_tunnel_nic_unregister() then observes work_pending as 0 and frees\nthe structure while the second work item is still active in the queue,\nleading to UAF.\n\nFix this by returning early in udp_tunnel_nic_device_sync() if\nwork_pending is already set, preventing redundant work queueing.(CVE-2026-72405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix err_chunk memory leaks in INIT handling\n\nWhen sctp_verify_init() encounters unrecognized parameters, it allocates an\nerr_chunk to report them. However, this chunk is leaked in several code\npaths:\n\n1. In sctp_sf_do_5_1B_init(), if security_sctp_assoc_request() fails after\n   sctp_verify_init() has populated err_chunk, the function returns\n   immediately without freeing it.\n\n2. In sctp_sf_do_unexpected_init(), the same leak occurs on the\n   security_sctp_assoc_request() failure path.\n\n3. In sctp_sf_do_unexpected_init(), on the success path after copying\n   unrecognized parameters to the INIT-ACK, the function returns without\n   freeing err_chunk, unlike sctp_sf_do_5_1B_init() which properly frees\n   it.\n\nFix all three leaks by adding sctp_chunk_free(err_chunk) calls before\nreturning in the error paths and on the success path in\nsctp_sf_do_unexpected_init().(CVE-2026-72413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid5: avoid R5_Overlap races while breaking stripe batches\n\nKCSAN report a race in break_stripe_batch_list() vs. raid5_make_request()\non sh-\u0026gt;dev[i].flags (plain word write vs. atomic bit op)..\n\nand .. one possible scenario is:\n\nCPU1                            CPU2\nbreak_stripe_batch_list(sh1)\n-\u0026gt; handle sh2\n-\u0026gt; lock(sh2)\n-\u0026gt; sh2-\u0026gt;batch_head = NULL\n-\u0026gt; unlock(sh2)\n-\u0026gt; test_and_clear_bit(R5_Overlap, sh2-\u0026gt;dev[i].flags)\n-\u0026gt; wake_up_bit(sh2-\u0026gt;dev[i].flags)\n                                raid5_make_request()\n                                -\u0026gt; add_all_stripe_bios(sh2)\n                                -\u0026gt; lock(sh2)\n                                -\u0026gt; stripe_bio_overlaps(sh2) returns true\n\t\t\t\t   batch_head is NULL, so new bio overlap\n\t\t\t\t   exist bio on sh2 -\u0026gt; true\n                                -\u0026gt; set_bit(R5_Overlap, sh2-\u0026gt;dev[i].flags)\n                                -\u0026gt; unlock(sh2)\n                                -\u0026gt; wait_on_bit(sh2-\u0026gt;dev[i].flags)\n-\u0026gt; sh2-\u0026gt;dev[i].flags = sh1-\u0026gt;dev[i].flags \u0026amp; ~R5_Overlap\n\nNo wait_up_bit(), CPU2 could be wait_on_bit() forever...\n\nFix by :\n- Expand the protect zone.\n- Use batch_head\u0026apos;s device flag\u0026apos;s snaphot when no held head_sh-\u0026gt;stripe_lock.\n- Move sh/head_sh-\u0026gt;batch_head = NULL to the end of protected zone , and ,\n  any concurrent add_all_stripe_bios() grabs sh-\u0026gt;stripe_lock now either:\n\t- see batch_head != null, and , is rejected by stripe_bio_overlaps()\n\t  under the lock (no R5_Overlap wait ) , or ,\n\t- sees batch_head == NULL, only after dev[i].flags has already been\n\t  set and the prior R5_Overlap waiters worken.\n\nKCSAN report:\n================================================\n  BUG: KCSAN: data-race in break_stripe_batch_list / raid5_make_request\n\n  write (marked) to 0xffff8e89c8117548 of 8 bytes by task 4042 on cpu 0:\n    raid5_make_request+0xea0/0x2930\n    md_handle_request+0x4a2/0xa40\n    md_submit_bio+0x109/0x1a0\n    __submit_bio+0x2ec/0x390\n    submit_bio_noacct_nocheck+0x457/0x710\n    submit_bio_noacct+0x2a7/0xc20\n    submit_bio+0x56/0x250\n    blkdev_direct_IO+0x54c/0xda0\n    blkdev_write_iter+0x38f/0x570\n    aio_write+0x22b/0x490\n    io_submit_one+0xa51/0xf70\n    __x64_sys_io_submit+0xf7/0x220\n    x64_sys_call+0x1907/0x1c60\n    do_syscall_64+0x130/0x570\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n  read to 0xffff8e89c8117548 of 8 bytes by task 4010 on cpu 5:\n    break_stripe_batch_list+0x249/0x480\n    handle_stripe_clean_event+0x720/0x9b0\n    handle_stripe+0x32fb/0x4500\n    handle_active_stripes.isra.0+0x6e0/0xa50\n    raid5d+0x7e0/0xba0\n    md_thread+0x15a/0x2d0\n    kthread+0x1e3/0x220\n    ret_from_fork+0x37a/0x410\n    ret_from_fork_asm+0x1a/0x30\n\n  value changed: 0x0000000000000019 -\u0026gt; 0x0000000000000099 --\u0026gt; R5_Overlap(CVE-2026-72420)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Guard conntrack opts error writes\n\nThe conntrack lookup and allocation kfuncs take an opts pointer\ntogether with an opts__sz argument. The verifier checks only the memory\nrange described by opts__sz, but the wrappers unconditionally write\nopts-\u0026gt;error whenever the internal lookup or allocation helper returns an\nerror.\n\nFor an invalid size smaller than the end of opts-\u0026gt;error, that write can\nland outside the verifier-checked range. Keep returning NULL for invalid\narguments, but only report the error through opts-\u0026gt;error when the\nsupplied size includes the field.\n\nThis preserves error reporting for the supported 12-byte and 16-byte\nlayouts, and for other invalid sizes that still include opts-\u0026gt;error.(CVE-2026-72423)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/bnxt_re: Proper rollback if the ioremap fails\n\nbnxt_qplib_alloc_dpi returns success even if ioremap fails.\nAdd the proper rollback when the ioremap fails and return\n-ENOMEM status.(CVE-2026-72496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: clear sock_ops cb flags before force-closing a child socket\n\nA child socket inherits the listener\u0026apos;s bpf_sock_ops_cb_flags via\nsk_clone_lock(). If its setup fails in tcp_v4_syn_recv_sock() /\ntcp_v6_syn_recv_sock(), the child is freed through put_and_exit, where\ninet_csk_prepare_forced_close() drops the socket lock and tcp_done() runs\nwithout it.\n\nIf BPF_SOCK_OPS_STATE_CB_FLAG was inherited, tcp_done() -\u0026gt; tcp_set_state()\ncalls tcp_call_bpf(), which expects the lock and trips sock_owned_by_me():\n\n  WARNING: include/net/sock.h:1799 at tcp_set_state+0x433/0x550\n  RIP: 0010:tcp_set_state+0x433/0x550 include/net/sock.h:1799\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_done+0xba/0x250 net/ipv4/tcp.c:5095\n   tcp_v4_syn_recv_sock+0x850/0xa50 net/ipv4/tcp_ipv4.c:1787\n   tcp_check_req+0xf30/0x1360 net/ipv4/tcp_minisocks.c:926\n   tcp_v4_rcv+0x1047/0x1b50 net/ipv4/tcp_ipv4.c:2164\n   \u0026lt;/IRQ\u0026gt;\n\nThe child is freed before it is ever established, so it should run no\nsock_ops callback. Clear its cb flags in inet_csk_prepare_for_destroy_sock(),\nthe common point for the IPv4, IPv6 and chtls forced-close paths and for the\nMPTCP -\u0026gt;syn_recv_sock() failure path (dispose_child), which reaches tcp_done()\non a child that was never established too.(CVE-2026-74268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: fib: Don\u0026apos;t dump dying fib_info in fib_leaf_notify().\n\nsyzbot reported use-after-free in nsim_fib4_prepare_event(). [0]\n\nThe problem is that the following functions call fib_info_hold() /\nrefcount_inc() while dumping fib_info under RCU, which is unsafe.\n\n  * mlxsw_sp_router_fib4_event()\n  * rocker_router_fib_event()\n  * nsim_fib4_prepare_event()\n\nrefcount_inc_not_zero() must be used, but it would be too late\nthere.\n\nLet\u0026apos;s guarantee the lifetime of fib_info in fib_leaf_notify().\n\nNote that IPv6 does not need the corresponding change since\nfib6_table_dump() holds fib6_table.tb6_lock.\n\n[0]:\nrefcount_t: addition on 0; use-after-free.\nWARNING: lib/refcount.c:25 at refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25, CPU#0: kworker/u8:15/3420\nModules linked in:\nCPU: 0 UID: 0 PID: 3420 Comm: kworker/u8:15 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026\nWorkqueue: netns cleanup_net\nRIP: 0010:refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25\nCode: eb 66 85 db 74 3e 83 fb 01 75 4c e8 1b f1 22 fd 48 8d 3d 84 cb f1 0a 67 48 0f b9 3a eb 4a e8 08 f1 22 fd 48 8d 3d 81 cb f1 0a \u0026lt;67\u0026gt; 48 0f b9 3a eb 37 e8 f5 f0 22 fd 48 8d 3d 7e cb f1 0a 67 48 0f\nRSP: 0018:ffffc9000f2c7270 EFLAGS: 00010293\nRAX: ffffffff84a18858 RBX: 0000000000000002 RCX: ffff888032ff9ec0\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8f9353e0\nRBP: 0000000000000000 R08: ffff888032ff9ec0 R09: 0000000000000005\nR10: 0000000000000100 R11: 0000000000000004 R12: ffff8880570cc000\nR13: dffffc0000000000 R14: ffff88802b40563c R15: ffff8880570cc000\nFS:  0000000000000000(0000) GS:ffff888126173000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fb1f4d5d000 CR3: 000000006072a000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __refcount_add include/linux/refcount.h:-1 [inline]\n __refcount_inc include/linux/refcount.h:366 [inline]\n refcount_inc include/linux/refcount.h:383 [inline]\n fib_info_hold include/net/ip_fib.h:629 [inline]\n nsim_fib4_prepare_event drivers/net/netdevsim/fib.c:930 [inline]\n nsim_fib_event_schedule_work drivers/net/netdevsim/fib.c:1000 [inline]\n nsim_fib_event_nb+0x1055/0x1240 drivers/net/netdevsim/fib.c:1043\n call_fib_notifier+0x45/0x80 net/core/fib_notifier.c:25\n call_fib_entry_notifier net/ipv4/fib_trie.c:90 [inline]\n fib_leaf_notify net/ipv4/fib_trie.c:2176 [inline]\n fib_table_notify net/ipv4/fib_trie.c:2194 [inline]\n fib_notify+0x36b/0x5e0 net/ipv4/fib_trie.c:2217\n fib_net_dump net/core/fib_notifier.c:70 [inline]\n register_fib_notifier+0x184/0x360 net/core/fib_notifier.c:108\n nsim_fib_create+0x85d/0x9f0 drivers/net/netdevsim/fib.c:1596\n nsim_dev_reload_create drivers/net/netdevsim/dev.c:1604 [inline]\n nsim_dev_reload_up+0x374/0x7c0 drivers/net/netdevsim/dev.c:1058\n devlink_reload+0x501/0x8d0 net/devlink/dev.c:475\n devlink_pernet_pre_exit+0x1ff/0x420 net/devlink/core.c:558\n ops_pre_exit_list net/core/net_namespace.c:161 [inline]\n ops_undo_list+0x187/0x940 net/core/net_namespace.c:234\n cleanup_net+0x56e/0x800 net/core/net_namespace.c:702\n process_one_work kernel/workqueue.c:3314 [inline]\n process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397\n worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478\n kthread+0x388/0x470 kernel/kthread.c:436\n ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;(CVE-2026-74289)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix UAF in hci_unregister_dev()\n\nhci_unregister_dev() does not disable cmd_timer and ncmd_timer\nbefore the hci_dev structure is freed. If a timeout fires\nduring device teardown, the callback dereferences freed memory\n(including the hdev-\u0026gt;reset function pointer), leading to a\nuse-after-free.\n\nAdd disable_delayed_work_sync() calls alongside the existing\ndisable_work_sync() calls to ensure both timers are fully\nquiesced before teardown proceeds.(CVE-2026-74302)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nixgbe: do not configure xps for XDP queues\n\nnetif_set_xps_queue() should not be called for an XDP Tx queue, since such\nqueues are not netdev-exposed. On systems with number of CPUs \u0026gt;=64, on E610\nadapter, netdev is configured with maximum number queue pairs being 63\n(due to MSI-X assignment), but configuring XDP results in 64 XDP queues.\n\nSo, during XDP program load, when netif_set_xps_queue() is called for the\nlast XDP queue, we get a WARNING with a call trace and KASAN report\nafterwards (if enabled).\n\n[ 2012.699800] WARNING: net/core/dev.c:2854 at __netif_set_xps_queue+0x116a/0x1e40, CPU#36: xdpsock/103668\n[...]\n[ 2012.700029] RIP: 0010:__netif_set_xps_queue+0x116a/0x1e40\n[ 2012.700035] Code: b6 34 06 48 89 f8 83 e0 07 83 c0 01 40 38 f0 7c 09 40 84 f6 0f 85 03 0a 00 00 0f b7 44 24 40 66 43 89 44 6a 18 e9 01 fb ff ff \u0026lt;0f\u0026gt; 0b e9 f2 ee ff ff 44 8b 44 24 44 45 85 c0 74 50 4d 85 e4 0f 84\n[ 2012.700040] RSP: 0018:ffff8882369aeb28 EFLAGS: 00010246\n[ 2012.700046] RAX: 0000000000000000 RBX: 000000000000003f RCX: 0000000000000000\n[ 2012.700050] RDX: 1ffff1111da3d891 RSI: ffff888120e34250 RDI: ffff8888ed1ec488\n[ 2012.700054] RBP: ffff888913281560 R08: 0000000000000000 R09: ffff8888ed1ec000\n[ 2012.700058] R10: ffff8888a2e83180 R11: 0000000000000000 R12: 0000000000007fa8\n[ 2012.700061] R13: 000000000000003f R14: ffff888120e34854 R15: ffff8889132817c8\n[ 2012.700065] FS:  00007fc8ea9ff740(0000) GS:ffff88884cefe000(0000) knlGS:0000000000000000\n[ 2012.700069] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 2012.700073] CR2: 00007f81c8000020 CR3: 00000002299f8006 CR4: 00000000007726f0\n[ 2012.700077] PKRU: 55555554\n[ 2012.700080] Call Trace:\n[ 2012.700084]  \u0026lt;TASK\u0026gt;\n[ 2012.700087]  ? ktime_get+0x61/0x150\n[ 2012.700097]  ? usleep_range_state+0x133/0x1b0\n[ 2012.700108]  ? __pfx_usleep_range_state+0x10/0x10\n[ 2012.700114]  netif_set_xps_queue+0x31/0x50\n[ 2012.700119]  ixgbe_configure_tx_ring+0x472/0x920 [ixgbe]\n[...]\n[ 2012.700486]  ixgbe_xdp+0x38f/0x750 [ixgbe]\n\n[...]\n\n[ 2012.701094] BUG: KASAN: slab-out-of-bounds in __netif_set_xps_queue+0x1ac5/0x1e40\n[ 2012.701100] Write of size 4 at addr ffff88888d43cff8 by task xdpsock/103668\n\nSkip XPS configuration for XDP Tx queues.(CVE-2026-74317)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvhost: fix vhost_get_avail_idx for a non empty ring\n\nvhost_get_avail_idx is supposed to report whether it has updated\nvq-\u0026gt;avail_idx. Instead, it returns whether all entries have been\nconsumed, which is usually the same. But not always - in\ndrivers/vhost/net.c and when mergeable buffers have been enabled, the\ndriver checks whether the combined entries are big enough to store an\nincoming packet. If not, the driver re-enables notifications with\navailable entries still in the ring. The incorrect return value from\nvhost_get_avail_idx propagates through vhost_enable_notify and causes\nthe host to livelock if the guest is not making progress, as vhost will\nimmediately disable notifications and retry using the available entries.\n\nThis goes back to commit d3bb267bbdcb (\u0026quot;vhost: cache avail index in\nvhost_enable_notify()\u0026quot;) which changed vhost_enable_notify() to compare\nthe freshly read avail index against vq-\u0026gt;last_avail_idx instead of the\npreviously cached vq-\u0026gt;avail_idx. Commit 7ad472397667 (\u0026quot;vhost: move\nsmp_rmb() into vhost_get_avail_idx()\u0026quot;) then carried over the same\ncomparison when refactoring vhost_enable_notify() to call the unified\nvhost_get_avail_idx().\n\nThe obvious fix is to make vhost_get_avail_idx do what the comment\nsays it does and report whether new entries have been added.(CVE-2026-74356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1,raid10: fix deadlock in read error recovery path\n\nraid1d and raid10d may resubmit a split md cloned bio while handling\na read error. In this case, resubmitting the bio can lead to a deadlock\nif the array is suspended before md_handle_request() acquires an\nactive_io reference via percpu_ref_tryget_live().\n\nSince the cloned bio already holds an active_io reference,\ntrying to acquire another reference via percpu_ref_tryget_live()\ncan lead to a deadlock while the array is suspended.\n\nFix this by using percpu_ref_get() for md cloned bios.(CVE-2026-74375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fix page fragment cache leak in error path\n\nIn nvmet_tcp_alloc_queue(), when a connection is closed during the\nallocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN),\nthe error handling jumps to out_destroy_sq and then to out_ida_remove\nwithout draining the page fragment cache.\n\nAlthough nvmet_tcp_free_cmd() is called in some error paths to release\nindividual page fragments, the underlying page cache reference held by\nqueue-\u0026gt;pf_cache is never released. The first allocation using pf_cache\nis the call to nvmet_tcp_alloc_cmd() for queue-\u0026gt;connect, which happens\nafter ida_alloc() returns successfully. This results in a page leak each\ntime a connection fails during allocation, which could lead to memory\nexhaustion over time if connections are repeatedly opened and closed.\n\nFix this by calling page_frag_cache_drain() before freeing the queue\nstructure in the out_ida_remove label.(CVE-2026-74386)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: use pskb_network_may_pull() in route_shortcircuit()\n\nroute_shortcircuit() currently calls pskb_may_pull(skb, sizeof(struct iphdr))\n(or ipv6hdr), which checks if bytes are available starting from skb-\u0026gt;data.\n\nHowever, in vxlan_xmit(), skb-\u0026gt;data points to the MAC header, so\nskb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, 20)\nonly checks 20 bytes from skb-\u0026gt;data (which is 14 bytes MAC header + 6 bytes of\nIP header), leaving the rest of the IP header potentially un-pulled in non-linear\nfrags. Subsequent dereferences of ip_hdr(skb)-\u0026gt;daddr can read beyond the pulled\nlinear buffer length.\n\nFix this by using pskb_network_may_pull(), which adds skb_network_offset(skb) to\nthe length check to ensure the full network header is present in the linear buffer.(CVE-2026-74473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: use neigh_ha_snapshot() in route_shortcircuit()\n\nThe neighbour hardware address n-\u0026gt;ha can be updated asynchronously by the\nneighbour subsystem, protected by n-\u0026gt;ha_lock seqlock. Reading n-\u0026gt;ha without\nholding the seqlock loop can lead to torn reads or reading a partially updated\nMAC address.\n\nUse neigh_ha_snapshot() in route_shortcircuit() to safely copy n-\u0026gt;ha under\nread_seqbegin()/read_seqretry() lock protection before using it.\n\nNote that arp_reduce() and neigh_reduce() seem to have the same issue\nleft for future patches.(CVE-2026-74475)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nveth: convert frag_list skbs before running XDP\n\nA frag_list skb can reach veth with data_len set but nr_frags zero.\nveth_convert_skb_to_xdp_buff() only converts skbs that are shared,\nlocked, have frags[], or do not have enough headroom. It later uses\nskb_is_nonlinear() to decide whether to set XDP_FLAGS_HAS_FRAGS and\nxdp_frags_size.\n\nThat exposes frag_list data to XDP as if it were stored in frags[], but\nfrags[] is empty. AF_XDP copy mode can then trust the bogus XDP fragment\nmetadata, walk an empty fragment entry, and crash in memcpy() from\n__xsk_rcv().\n\nRoute non-linear skbs through skb_pp_cow_data() before exposing them to\nXDP, and only advertise XDP frags when the resulting skb has frags[].\nskb_copy_bits() already handles frag_list input, and skb_pp_cow_data()\nbuilds frags[] output with skb_add_rx_frag(), which is the\nrepresentation XDP multi-buffer expects.(CVE-2026-74476)\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/page_reporting: use system_freezable_wq to fix UAF during suspend. During PM freeze (e.g. S3 suspend or S4 hibernation), device drivers like virtio_balloon reset their underlying virtio devices and delete their virtqueues via vdev-\u0026gt;config-\u0026gt;del_vqs(). However, page reporting work (page_reporting_process) was scheduled on the global system_wq. Because system_wq lacks the WQ_FREEZABLE flag, the PM freezer skips it, leaving page_reporting_process active during suspend. If pages are freed into the buddy allocator while suspending, page reporting triggers virtballoon_free_page_report() on deleted virtqueues, resulting in a Use-After-Free / General Protection Fault.(CVE-2026-74481)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: reject a flag character as the field delimiter\n\nThe registration string starts with a user chosen delimiter that separates the individual fields. So that the field parsers terminate even on a truncated string create_entry() pads the buffer with that same delimiter.\n\nMost fields are scanned for the delimiter with strchr()/scanarg() and happily stop on the padding. The flags field is different: instead of scanning for the delimiter check_special_flags() consumes the flag characters \u0026apos;P\u0026apos;, \u0026apos;O\u0026apos;, \u0026apos;C\u0026apos; and \u0026apos;F\u0026apos; and stops at the first byte that is none of them, relying on the trailing delimiter to end the scan.\n\nIf the delimiter is itself a flag character the padding no longer acts as a terminator. The scan swallows all eight padding bytes and keeps reading past the end of the allocation until it hits a byte that is not a flag character.(CVE-2026-74485)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbinfmt_misc: restore write access when removing an entry\n\nRegistering an entry with the MISC_FMT_OPEN_FILE flag opens the\ninterpreter via open_exec() which denies write access to it for as\nlong as the entry exists. Removing the entry closes the interpreter\nfile via filp_close() but never restores write access, leaving the\ninode\u0026apos;s i_writecount permanently negative. Opening the interpreter\nfor writing keeps failing with ETXTBSY long after the entry is gone\nuntil the inode is evicted from the inode cache.\n\nCommit 90f601b497d7 (\u0026quot;binfmt_misc: restore write access before\nclosing files opened by open_exec()\u0026quot;) fixed the same imbalance in the\nerror path of bm_register_write() but the actual removal path has\nbeen leaking the write denial since the introduction of the flag.\n\nRestore write access in put_binfmt_handler() before closing the\ninterpreter file.(CVE-2026-74487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nALSA: usb-audio: fix OOB write in snd_usbmidi_akai_output()\\n\\nsnd_usbmidi_akai_output() computes its fill-loop bound\\n\\n\\tbuf_end = ep-\u0026gt;max_transfer - MAX_AKAI_SYSEX_LEN - 1;\\n\\nas a signed int, so a small device-advertised bulk-OUT max_transfer\\nmakes buf_end negative.  The loop guard then compares the u32\\nurb-\u0026gt;transfer_buffer_length against that negative int: the usual\\narithmetic conversion turns buf_end into a large unsigned value, so the\\nguard stays true and each iteration keeps appending SysEx framing and\\npayload bytes past the end of the URB transfer buffer, which is only\\nmax_transfer bytes long.\\n\\nA USB device that advertises a tiny bulk-OUT endpoint can therefore\\ntrigger an attacker-length- and content-controlled heap out-of-bounds\\nwrite when a process writes to the created /dev/snd/midiC*D* node.\\n\\nReturn early when there is no room for even one SysEx, so the loop is\\nnever entered with a bound that would wrap.  The loop is the last\\nstatement of the function, so bailing out is equivalent to it not\\nrunning.\\n\\nDiscovered by XBOW, triaged by Baul Lee \u0026amp;lt;baul.lee@xbow.com\u0026amp;gt;(CVE-2026-74499)\n\nIn the Linux kernel, a use-after-free (UAF) vulnerability exists in the Bluetooth HCI sync module. hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev-\u0026gt;lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can interleave, causing a use-after-free of the adv_info pointer, leading to a slab-use-after-free error as detected by KASAN. An attacker could potentially exploit this vulnerability to cause a system crash or potential information disclosure.(CVE-2026-74509)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: pci: Fix memory accounting for pinned/unpinned pages\n\nThe account_mem() and unaccount_mem() functions call get_uid() which\nincrements the reference count of struct user_struct on every invocation.\nBut we don\u0026apos;t decrement the count by calling free_uid(). It also\naccounted/unaccounted the pages against the current-\u0026gt;mm. But its possible\nthe unaccount_mem() can be called from a different process context than the\none that originally pinned the pages.\n\nLet\u0026apos;s fix this by storing the pinning process user_struct and mm_struct\nwhen accounting for pinned pages, and subsequently free these resources\nwhen the pages are unpinned.\n\n[(CVE-2026-74514)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/iommufd: Fix IOPF group ownership UAF\n\niopf_group_alloc() links each last-page IOPF group into the generic IOPF\npending list before invoking the domain fault handler.\niommufd_fault_iopf_handler() also queued an accepted group in the\nIOMMUFD deliver list without removing it from the generic pending list.\n\nWhen detach or HWPT replacement drops the device\u0026apos;s IOPF reference count\nto zero, an IOMMU driver may call iopf_queue_remove_device(). That\nfunction responds to and frees groups through the generic pending list\nwithout removing the same groups from IOMMUFD\u0026apos;s deliver list or response\nxarray. A later read, response, or cleanup can then access the freed\ngroup and cause a UAF.\n\nFix this by dequeuing an accepted group from the generic pending list\nbefore IOMMUFD queues it for userspace response.\nMake iopf_group_response() send a response regardless of pending-list\nmembership, so the dequeued group can still be completed by IOMMUFD.(CVE-2026-74520)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: fix leaking sk after socket release\n\niso_sock_kill() tests !sock_flag(sk, SOCK_ZAPPED) || sk-\u0026gt;sk_socket ||\nsock_flag(sk, SOCK_DEAD) for early return, but this is always true since\nsock_orphan(sk) sets SOCK_DEAD, so the sk reference released by socket\nalways leaks, iso_sock_destruct is never called.\n\nThe socket reference also leaks when __iso_sock_close() does not set\nSOCK_ZAPPED, since iso_conn_del() does not call iso_sock_kill() after\nzapping.\n\nFix by replacing SOCK_DEAD by BT_SK_KILLED flag that is not used for\nsomething else, and lock_sock to ensure iso_sock_kill() puts sk only\nafter socket release only once. Release and iso_conn_del may run\nconcurrently. Call iso_sock_kill() from iso_conn_del() to clean sk up\nafter zapping.\n\nRemove call to iso_sock_kill() from iso_sock_close(), as it\u0026apos;s generally\nno-op there.(CVE-2026-74536)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()\n\nsyzbot reported a memory leak [1] in the UDP tunnel NIC offload code.\n\nWhen device registration fails (e.g. in register_netdevice()), netdev core\nunwinds by sending a single NETDEV_UNREGISTER notification. If work was queued\nduring NETDEV_REGISTER (utn-\u0026gt;work_pending is set), udp_tunnel_nic_unregister()\nreturns early:\n\n\tif (utn-\u0026gt;work_pending)\n\t\treturn;\n\nBecause failed registrations do not enter netdev_wait_allrefs_any(), no\nsubsequent NETDEV_UNREGISTER rebroadcast will ever occur. As a result, the\nstruct udp_tunnel_nic allocated in udp_tunnel_nic_alloc() is leaked\npermanently.\n\nFix this by removing the early return. Instead, synchronously cancel any\npending work with cancel_delayed_work_sync() before freeing @utn.\n\nTo be able to call cancel_delayed_work_sync() while holding RTNL (the work also\nneeds RTNL), switch udp_tunnel_nic_device_sync_work() to rtnl_trylock(). If RTNL\nis contended, requeue the work with a 1 jiffy delay (via queue_delayed_work())\nto prevent high CPU contention while waiting for RTNL lock.\n\nThe utn-\u0026gt;work_pending bookkeeping is no longer needed and is removed, as\nthe workqueue core already tracks the pending/running state of the work.\n\n[1]\nBUG: memory leak\nunreferenced object 0xffff888127d5f840 (size 96):\n  comm \u0026quot;syz-executor\u0026quot;, pid 5806, jiffies 4294942188\n  backtrace (crc 99fdb6c8):\n    __kmalloc_noprof+0x3bf/0x550\n    udp_tunnel_nic_alloc net/ipv4/udp_tunnel_nic.c:756 [inline]\n    udp_tunnel_nic_register net/ipv4/udp_tunnel_nic.c:833 [inline]\n    udp_tunnel_nic_netdevice_event+0x804/0xab0 net/ipv4/udp_tunnel_nic.c:931\n    notifier_call_chain+0x59/0x160 kernel/notifier.c:85\n    call_netdevice_notifiers_info+0x7d/0xb0 net/core/dev.c:2250\n    register_netdevice+0xc10/0xeb0 net/core/dev.c:11478(CVE-2026-74543)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: validate offshift to prevent shift-out-of-bounds\n\nu32_change() copies the user-provided tc_u32_sel.offshift (unsigned char,\n0-255) into the kernel knode object without bounds validation. When a\npacket later hits u32_classify() with TC_U32_VAROFFSET set, it evaluates\n`ntohs(offmask \u0026amp; *data) \u0026gt;\u0026gt; offshift` where the left operand is a 16-bit\nvalue promoted to a 32-bit int. Any offshift \u0026gt;= 32 is undefined behavior\nper C11 6.5.7p3, triggerable by an unprivileged user via user/network\nnamespaces.\n\nUBSAN: shift-out-of-bounds in net/sched/cls_u32.c:236:43\nshift exponent 32 is too large for 32-bit type int\n\nFix this by rejecting offshift \u0026gt;= 16 during filter creation in\nu32_change().(CVE-2026-74544)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: make nft_object rhltable per table\n\nThe nft_object rhltable is global, this allows for accessing objects\nthat are being dismangled from lookup path by other existing netns.\nGiven the nft_obj_destroy() releases the object inmediately, this might\nlead to use-after-free of these objects that are being released.\nMake the existing rhltable per table to address this issue to deal with\nwith the nft_rcv_nl_event() path too.\n\nUpdate nft_obj_lookup() to take the table as non-const, otherwise,\ncompiler complains when passing the objname_ht to rhltable_lookup().(CVE-2026-74565)\n\nIn the Linux kernel, the following vulnerability has been resolved: sctp: clear new_transport when removing a peer. sctp_process_asconf_param() stores a newly added peer transport in asoc-\u0026gt;new_transport. After all parameters in the ASCONF chunk have been processed, sctp_sf_do_asconf() uses this pointer to send a HEARTBEAT to the new transport. An authenticated ASCONF from a remote SCTP peer can add a transport and remove it again with a wildcard DEL-IP parameter in the same chunk. The wildcard deletion preserves the transport on which the ASCONF arrived, but removes the newly added transport through sctp_assoc_del_nonprimary_peers(). The removal does not clear asoc-\u0026gt;new_transport, leaving it pointing to the removed transport. sctp_sf_do_asconf() then creates a HEARTBEAT whose chunk-\u0026gt;transport points to the removed transport without holding a transport reference. After the transport is freed by RCU, a successful ASCONF_ACK for the replacement address releases the queued HEARTBEAT and sctp_outq_select_transport() reads the freed transport\u0026apos;s state, leading to a use-after-free condition.(CVE-2026-74586)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nsctp: fix use-after-free of cached ASCONF chunk\\n\\naddip_last_asconf caches the outstanding outbound ASCONF chunk. The normal\\nASCONF-ACK completion path releases the chunk and clears the pointer.\\n\\nHowever, sctp_asconf_queue_teardown() releases the cached chunk without\\nclearing addip_last_asconf. During peer restart handling,\\nsctp_sf_do_dupcook_a() queues SCTP_CMD_PURGE_ASCONF_QUEUE, which invokes\\nsctp_asconf_queue_teardown() while the association remains alive and leaves\\nthe pointer dangling.\\n\\nA delayed authenticated ASCONF-ACK can then reach sctp_sf_do_asconf_ack(),\\nwhich accesses the stale chunk and passes it to sctp_process_asconf_ack(),\\ncausing a use-after-free and a second release.\\n\\nClearing the pointer exposes a race with T4 expiry. Peer restart handling\\nqueues the timer stop before the purge, but SCTP_CMD_TIMER_STOP uses\\ntimer_delete(), which does not wait for a callback already running on\\nanother CPU. Such a callback can reach sctp_sf_t4_timer_expire() after\\nthe purge and dereference NULL.\\n\\nClear addip_last_asconf after releasing the cached chunk, and make\\nsctp_sf_t4_timer_expire() consume a stale T4 expiry if no outstanding\\nASCONF remains.(CVE-2026-74587)\n\nIn the Linux kernel, the following vulnerability has been resolved: sctp: keep chunk-\u0026gt;transport in step with the list it is queued on. __sctp_outq_flush_rtx() moves a gap-acked chunk onto another transport\u0026apos;s transmitted list without updating chunk-\u0026gt;transport. The chunk then sits on a live transport\u0026apos;s list while chunk-\u0026gt;transport still names a different one. If that transport is removed - sctp_assoc_rm_peer() from an ASCONF Delete-IP - sctp_transport_free() RCU-frees it and the chunk is left with a dangling pointer. A SACK that reneges on the TSN clears the flag, and the next SACK reaches inside the freed transport. KASAN reports a slab-use-after-free read in sctp_check_transmitted(), freed from sctp_assoc_rm_peer().(CVE-2026-74588)\n\nIn the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix sk_redir use-after-free in send verdict. sk_psock_msg_verdict() takes a socket reference for psock-\u0026gt;sk_redir. tcp_bpf_send_verdict() copies that pointer while holding the source socket lock, but does not take a reference for the local copy before dropping the lock around tcp_bpf_sendmsg_redir(). When apply_bytes keeps the cached verdict active, another sendmsg() on the same source socket can consume the remaining bytes and release the cached reference while the first thread still holds only the raw local pointer, leading to a use-after-free. KASAN reported a slab-use-after-free error.(CVE-2026-74589)\n\nIn the Linux kernel, the following vulnerability has been resolved: eventfs: Use children field for rcu head and add memory barriers. When an eventfs inode is freed, it sets ei-\u0026gt;is_freed and then uses its ei-\u0026gt;list to add it to the srcu link list as the list field is a union with the rcu list head. As the ei-\u0026gt;list is used to iterate over an SRCU protected list without taking the eventfs_mutex, there\u0026apos;s nothing stopping the iteration over that list to see the ei-\u0026gt;rcu instead of the ei-\u0026gt;list and it will read a corrupt target.(CVE-2026-74605)\n\nIn the Linux kernel, the following vulnerability has been resolved: eventfs: Fix use-after-free in eventfs_remove_rec(). eventfs_remove_rec() recursively removes the child at the current loop position. After the recursive call returns, list_for_each_entry() advances by reading list.next from the removed child. If free_ei() drops the final reference, release_ei() reuses the list/rcu union to queue an SRCU callback. The child may be freed before that read. The eventfs_mutex serializes list updates, but it does not keep the removed child alive or prevent the SRCU callback from running.(CVE-2026-74606)\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: Fix use-after-free in cifs_try_adding_channels(). cifs_try_adding_channels() takes a temporary reference to an interface before dropping iface_lock. If cifs_ses_add_channel() fails, it drops that reference and then increments iface-\u0026gt;weight_fulfilled. A concurrent interface list refresh can remove the list reference while channel creation is in progress. In that case, the failure-path kref_put() releases the last reference and frees iface. Updating weight_fulfilled afterward then accesses freed memory.(CVE-2026-74608)\n\nIn the Linux kernel, the following vulnerability has been resolved: tipc: read le-\u0026gt;link under the node lock in tipc_node_link_down(). tipc_node_link_down() caches the link pointer before taking n-\u0026gt;lock. The delete=true caller frees that very object under n-\u0026gt;lock, so the lock does not protect the cached pointer against it. An in-flight CPU that has read l therefore dereferences freed memory once another CPU frees it: a use-after-free read in tipc_link_is_establishing(), and a use-after-free write via tipc_link_reset() on the establishing branch.(CVE-2026-74609)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: don\u0026apos;t leave a full plaintext sk_msg ring unpushed\n\nWhen the copy path in tls_sw_sendmsg_locked() adds the fragment that fills the plaintext sk_msg ring, it does not set full_record, so the record is left full and unpushed. A later splice() then adds to an already full ring: sk_msg_page_add() has no fullness check of its own, so sg.end wraps onto sg.start and the ring appears empty. Fragments added after that overwrite live entries, and sg.size no longer matches what is reachable between sg.start and sg.end, so pushing the record runs the scatterwalk off the end of the scatterlist.\n\nAn unprivileged user can trigger this on a loopback TCP socket with the \u0026quot;tls\u0026quot; ULP attached:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000008\n  RIP: 0010:memcpy_from_scatterwalk+0x32/0xc0\n  Call Trace:\n   skcipher_walk_next+0x1d1/0x2c0\n   gcm_encrypt_aesni_avx+0x1e9/0x220\n   bpf_exec_tx_verdict+0x3bb/0x860\n   tls_sw_sendmsg+0xa1a/0xca0\n   __sys_sendto+0x1da/0x1f0\n\nSet full_record in the copy path when the ring becomes full, and push a record that is already full on entry to the sendmsg loop.(CVE-2026-74610)\n\nIn the Linux kernel, the following vulnerability has been resolved: tls: rx: restore msg_iter before TLS 1.3 optimistic retry. tls_decrypt_sg() advances msg-\u0026gt;msg_iter when it maps user pages for the optimistic TLS 1.3 zero-copy path. If the decrypted record turns out not to be unpadded application data, tls_decrypt_sw() retries into a kernel skb, but leaves the iterator advanced. The subsequent copy from the skb then writes decrypted bytes again at a later point in the caller iovecs while recvmsg() reports only the post-retry length. A TLS peer can trigger this after the receiver enables TLS_RX_EXPECT_NO_PAD.(CVE-2026-74611)\n\nIn the Linux kernel, the veth driver has an skb length accounting error after XDP frag adjustment. veth exposes non-linear skb fragments through an xdp_buff. If an XDP program adjusts the fragment area, veth_xdp_rcv_skb() copies xdp_frags_size back to skb-\u0026gt;data_len but leaves skb-\u0026gt;len containing the old fragment contribution. After a fragment shrink, this makes skb_headlen() larger than the actual linear area. In the reproduced UDP receive path, __skb_datagram_iter() copied 1024 bytes past the actual linear tail to userspace, starting at struct skb_shared_info. Additionally, bpf_xdp_pull_data() can advance data_end while leaving frags present, and the old __skb_put(skb, off) triggers SKB_LINEAR_ASSERT().(CVE-2026-74612)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nvsock/virtio: read virtqueues under worker locks\\n\\nCommit bd50c5dc182b (\u0026quot;vsock/virtio: add support for device suspend/resume\u0026quot;) made the *_run flags transition from false to true when restore installs replacement virtqueues. The RX, TX and event workers read their virtqueue before locking and checking the corresponding flag, so a worker delayed across freeze and restore can observe the replacement queue\u0026apos;s running state while retaining a pointer to the deleted queue.\\n\\nRead each virtqueue under its mutex after checking the run flag, keeping the pointer and state in the same queue generation.(CVE-2026-74614)\n\nIn the Linux kernel, the following vulnerability has been resolved: vxlan: do not arm the ageing timer on a device that is down. vxlan_changelink() arms vxlan-\u0026gt;age_timer whenever the requested ageing interval differs from the configured one, but there is no netif_running() test, so the timer is armed even on a device that was never brought up. The only synchronous cancel in the driver is the timer_delete_sync() in vxlan_stop(), which is .ndo_stop. netif_close_many() drops devices without IFF_UP before __dev_close_many() runs, so that cancel is skipped for such a device. When free_netdev() releases the allocation, the timer lives in freed memory while still queued on a timer_base, causing a use-after-free condition that can lead to system crash or code execution.(CVE-2026-74615)\n\nIn the Linux kernel, the following vulnerability has been resolved: xdp: reject clones that overrun skb_shared_info tailroom. xdpf_clone() clones broadcast copies into a single page and sets frame_sz to PAGE_SIZE. __xdp_build_skb_from_frame() later treats that page like a normal XDP frame and expects the usual skb_shared_info tailroom at the end of the buffer. The current check only rejects frames whose linear xdp_frame header, headroom, and packet data exceed PAGE_SIZE. A source frame backed by a larger allocation can still satisfy that check while extending into the clone\u0026apos;s required shared-info area. When such a clone is converted back into an skb, build_skb_around() places skb_shared_info over live packet bytes and later writes can corrupt XDP return metadata. Reject clones unless their linear area fits inside SKB_WITH_OVERHEAD(PAGE_SIZE), matching the tailroom requirement already enforced by the XDP-to-skb conversion path.(CVE-2026-74616)\n\nIn the Linux kernel, an input validation vulnerability exists in the net/sched subsystem. The act_gact and act_police modules lack range checking on the fallback control action. The tcf_action_check_ctrlact() function performs range checking on the primary control action, but act_gact and act_police each carry a second, independent control action supplied by user space (TCA_GACT_PROB.paction and TCA_POLICE_RESULT) that never reaches that helper. User space can set TC_ACT_CONSUMED (TC_ACT_VALUE_MAX + 1), which tells callers the action took ownership of the skb, resulting in memory leaks of sk_buff and its data buffer - one leaked sk_buff per packet traversing the filter.(CVE-2026-74620)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: atlantic: free stranded TX buffers on ring deinit\\n\\naq_vec_deinit() drains the TX rings with a single aq_ring_tx_clean() call, which frees at most AQ_CFG_TX_CLEAN_BUDGET (256) descriptors and stops at hw_head, which no longer moves once aq_vec_stop() has stopped the hardware and NAPI. Completed descriptors beyond the budget and everything still posted in [hw_head, sw_tail) keep their skb or xdp_frame when the interface goes down: aq_vec_ring_free() then frees the buffer ring and the references are lost for good.\\n\\nToday this is a silent memory leak on every interface down under TX/XDP_TX load. With the conversion of the RX path to page_pool posted for net-next it becomes much more visible: XDP_TX frames carry fragment references on the RX ring\u0026apos;s page_pool, so a single stranded frame keeps the pool\u0026apos;s inflight count above zero forever. page_pool_destroy() then never completes, the pool is leaked together with its pages, and \\\u0026quot;page_pool_release_retry() stalled pool shutdown\\\u0026quot; is warned every 60 seconds from that point on, on every ifdown, XDP detach or ring resize under XDP_TX load.(CVE-2026-74623)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conntrack: defer invalid log until after unlock\n\nTCP and SCTP conntrack paths can emit invalid-packet logs while ct-\u0026gt;lock is still held.\n\nWhen invalid logging is routed to nfnetlink_log and conntrack export is enabled, the log path can re-enter conntrack netlink glue and dump the same conntrack again. Protocol attribute dumping may take ct-\u0026gt;lock, so logging while holding that lock can deadlock.\n\nDefer the TCP invalid logs by storing only the minimal log context while ct-\u0026gt;lock is held and emitting the log after unlocking. Also make the TCP timeout-lowering invalid path return whether a log is needed, then emit that log after unlocking.\n\nDo the same for the SCTP invalid state-transition log that can be reached while ct-\u0026gt;lock is held.\n\nAdd a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers that log invalid conntracks while holding ct-\u0026gt;lock are caught outside TCP and SCTP as well.(CVE-2026-74624)\n\nIn the Linux kernel, the following vulnerability has been resolved: tracing: Fix race between update_event_fields and event_define_fields. The following sequence may lead to a race between event_define_fields() and update_event_fields(): CPU0 (loads module A) and CPU1 (loads module B) executing concurrently, where access to class-\u0026gt;fields is not protected by event_mutex in trace_event_update_all(), leading to a kernel panic. Fix by taking event_mutex in trace_event_update_all() before trace_event_sem.(CVE-2026-74636)\n\nIn the Linux kernel, the following vulnerability has been resolved: perf/core: Fix group leader use-after-free after sibling detach. perf_group_detach() handles leader and sibling detach differently. When a sibling is detached, it is removed from the leader\u0026apos;s sibling_list, but its group_leader pointer is left pointing at the old leader. This is not safe when the sibling is detached but kept alive, such as during CPU hotplug with DETACH_GROUP. A PERF_IOC_FLAG_GROUP ioctl on the sibling follows the stale group_leader pointer and dereferences the freed leader\u0026apos;s context, leading to a use-after-free condition.(CVE-2026-74637)\n\nIn the Linux kernel, the following vulnerability has been resolved: ipv4: fix use-after-free in fib_nhc_update_mtu(). fib_nhc_update_mtu() walks the nexthop exception table under RTNL, but RTNL does not serialize this walk with PMTU exception updates. The walk uses rcu_dereference_protected() with a constant true condition without holding fnhe_lock. The following interleaving can therefore occur: CPU 0 (fib_nhc_update_mtu) loads fnhe while CPU 1 (update_or_create_fnhe) holds fnhe_lock, calls fnhe_remove_oldest() to unlink fnhe, and kfree_rcu(fnhe, rcu). CPU 0 then accesses fnhe after grace period, causing a use-after-free. KASAN reported: BUG: KASAN: slab-use-after-free in fib_nhc_update_mtu+0x3df/0x410.(CVE-2026-74656)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ebt_nflog: pin the NFLOG backend\n\nnf_log_unregister() runs after the per-net teardown so its final RCU grace period also drains readers that obtained the logger from a per-net binding. However, ebt_nflog passes an explicit ULOG log type to nf_log_packet() without holding a reference on the selected logger module, unlike the xt_NFLOG and nft_log frontends.\n\nAn ebtables nflog rule can therefore remain callable while nfnetlink_log is unloaded. The resulting interleaving causes a use-after-free condition where CPU 1 dereferences per-net state after CPU 0 has freed it.(CVE-2026-74660)\n\nIn the Linux kernel, the following vulnerability has been resolved: inet: frags: publish queues before arming timer. inet_frag_create() arms the fragment queue timer before inserting the queue into the fqdir rhashtable. If the namespace fragment timeout is zero or negative, the timer can run before the queue is published. The timer callback then marks the queue complete, tries to remove a node that is not in the hash table yet, and drops the anticipated hash reference. Creation can subsequently publish the completed queue without restoring that reference, leaving a stale hash node after the caller drops the remaining reference. Publish the queue first and arm the timer while holding the queue lock. This makes timer expiry wait until the queue is visible in the hash table, so inet_frag_kill() can remove the node and balance the hash reference.(CVE-2026-74662)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\npacket: synchronize pressure clearing with ring reconfiguration\\n\\npacket_set_ring() updates the RX ring state under sk_receive_queue.lock, but used to publish the tpacket receive mode through po-\u0026gt;prot_hook.func after releasing that lock. packet_poll() and packet_recvmsg() can then run the pressure clearing path after the ring has been cleared while still seeing tpacket_rcv, causing __packet_rcv_has_room() to dereference stale or NULL ring storage.(CVE-2026-74666)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/packet: reset the MAC header on the packet-socket transmit path\n\npacket_parse_headers() resets the MAC header only for a SOCK_RAW frame whose socket did not bind a protocol. A protocol-bound SOCK_RAW socket, any SOCK_DGRAM frame, and the legacy SOCK_PACKET path therefore leave skb-\u0026gt;mac_header unset here.\n\nFor frames sent via __dev_queue_xmit() this is harmless: it resets the MAC header unconditionally. But the packet-socket PACKET_QDISC_BYPASS path uses dev_direct_xmit(), which does not, so the frame reaches ndo_start_xmit() with the MAC header unset. A driver that reads eth_hdr(skb) on transmit then dereferences skb-\u0026gt;head + (u16)~0, an out-of-bounds access ~64 KiB past the head -- the same class fixed for one consumer in commit f5089008f90c (\u0026quot;macsec: do not read an unset MAC header in macsec_encrypt()\u0026quot;).\n\npacket_parse_headers() runs only on the transmit path, where skb-\u0026gt;data points at the start of the L2 header for every packet-socket type regardless of its length: SOCK_RAW and SOCK_PACKET carry a user-supplied header and SOCK_DGRAM has one built by dev_hard_header(). Reset the MAC header unconditionally, mirroring __dev_queue_xmit(), so the frame is anchored on the bypass path too.\n\nFound by 0sec (https://0sec.ai) using automated source analysis; verified against source and matched to the macsec KASAN report in f5089008f90c. Compile-tested.(CVE-2026-74667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npacket: use consistent hard_header_len in TX_RING send path\n\ntpacket_snd() reads dev-\u0026gt;hard_header_len independently for skb allocation and header construction in tpacket_fill_skb(). Concurrent netdevice reconfiguration can therefore make the reserved headroom smaller than the amount later pushed, or make copylen - hard_header_len negative.\n\nSnapshot hard_header_len once before processing ring frames and use it for the frame limit, headroom allocation, copy length, and skb construction. Pass the snapshot to tpacket_fill_skb().\n\nThe separate SOCK_DGRAM consistency problem between hard_header_len and header_ops-\u0026gt;create is not addressed here.(CVE-2026-74668)\n\nIn the Linux kernel, the following vulnerability has been resolved: ipvs: clear IPv4 options after rebasing tunnel ICMP errors. ip_vs_in_icmp() rebases an skb from the outer ICMP packet to the quoted original request before passing it to icmp_send(). However, IPCB(skb)-\u0026gt;opt still describes the outer IPv4 header. A timestamp option in the outer header can therefore leave an offset that points into the quoted transport header after the rebase. __ip_options_echo() treats a byte at that stale location as the option length and copies it into the fixed-size option storage on the __icmp_send() stack, causing a stack out-of-bounds write.(CVE-2026-74669)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: stop estimator after disabled calc phase\n\nIPVS estimator kthread 0 starts with zeroed chain and tick limits until its initial calculation phase completes. If network namespace teardown clears ipvs-\u0026gt;enable during that phase, ip_vs_est_calc_phase() can return without installing positive limits.\n\nThe kthread can then continue into its main loop and drain est_temp_list with zero chain_max, tick_max and est_max_count values. Each enqueue consumes one available tick row, but est_count never reaches the zero est_max_count value. After all rows are consumed, the row lookup returns IPVS_EST_NTICKS and ip_vs_enqueue_estimator() writes past the ticks and tick_len arrays, causing a buffer overflow.\n\nExit kthread 0 after the calculation phase if the kthread is stopping or IPVS has been disabled. That keeps temporary estimators from being drained after the limits failed to initialize.\n\nEstimator kthreads can now self-exit before teardown or reload stops kd-\u0026gt;task. Keep an extra task reference after creation and release it with kthread_stop_put(), so kd-\u0026gt;task remains valid until the stop paths consume that reference.(CVE-2026-74670)\n\nIn the Linux kernel, the following vulnerability has been resolved: Input: evdev - fix information leak in evdev_pass_values(). In evdev_pass_values(), the input_event structure is allocated on the kernel stack and populated field-by-field. However, it is never fully initialized. On architectures where struct input_event contains explicit or implicit padding (such as the 32-bit __pad field on SPARC64), these padding bytes are left uninitialized. When this event structure is subsequently passed to the client buffer and later copied to userspace, the uninitialized padding bytes leak kernel stack memory, potentially exposing sensitive information. Similar issues exist in __evdev_queue_syn_dropped and __pass_event. Fix this by explicitly zeroing the entire event structure with memset() before populating its fields. This ensures all padding bytes are cleared before the data crosses the security boundary.(CVE-2026-74673)\n\nIn the Linux kernel, the following vulnerability has been resolved: Input: evdev - sanitize event type index when fetching event masks. The user-supplied event type index passed to EVIOCGMASK / EVIOCSMASK ioctls is used to index the static counts array in evdev_get_mask_cnt() and client evmasks array in evdev_get_mask(). While the event type is architecturally bounded by EV_CNT, speculative execution may mispredict bounds checks and perform out-of-bounds loads. Sanitize the event type index in evdev_get_mask_cnt() branchlessly using array_index_mask_nospec(). This clamps the index to 0 for safe array access and forces the returned count to 0 speculatively when the index is out of bounds, preventing any speculative memory access to client evmasks array.(CVE-2026-74683)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: tap: set skb-\u0026gt;dev before parsing virtio net header in tap_get_user_xdp()\\n\\nThe commit 4f61f133f354 (\u0026quot;net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-\u0026gt;dev is null\u0026quot;) fixed a crash in tap_get_user() by assigning skb-\u0026gt;dev before calling tun_vnet_hdr_to_skb(). This is required because virtio_net_hdr_to_skb() may invoke dev_parse_header_protocol(), which dereferences skb-\u0026gt;dev. Without the assignment, a NULL pointer dereference can occur.\\n\\nHowever, tap_get_user_xdp() still parses the virtio-net header before assigning skb-\u0026gt;dev. When the vhost TX path passes an XDP buffer containing a GSO virtio-net header but the protocol is set to zero on purpose, tun_vnet_hdr_to_skb() can reach dev_parse_header_protocol() while skb-\u0026gt;dev is still NULL, resulting in a crash.\\n\\nFix this by looking up the tap device and assigning skb-\u0026gt;dev before calling tun_vnet_hdr_to_skb(), matching the ordering already used in tap_get_user(). Preserve the existing RCU read-side critical section across dev_queue_xmit().(CVE-2026-74684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nsctp: clear control chunk transport if it is being removed\\n\\nsctp_make_heartbeat_ack() caches the destination transport in chunk-\u0026gt;transport without taking a reference. When src_out_of_asoc_ok is enabled, the HEARTBEAT ACK may remain queued on control_chunk_list instead of being transmitted immediately.\\n\\nIf the peer transport is removed while the chunk is still queued, sctp_assoc_rm_peer() drops the transport and schedules it for RCU freeing, but only clears cached transport pointers in out_chunk_list. The queued control chunk therefore retains a dangling transport pointer.\\n\\nOnce an ASCONF_ACK clears the suppression and the queued control chunk is transmitted, SCTP dereferences the stale transport pointer, leading to a use-after-free.\\n\\nFix this by also clearing chunk-\u0026gt;transport for queued control chunks in control_chunk_list when removing the transport.(CVE-2026-74688)\n\nIn the Linux kernel, the following vulnerability has been resolved: tcp: fix TFO max_qlen accounting across reuseport migration. A listener\u0026apos;s TCP_FASTOPEN max_qlen stops being accurate and lets through far more pending Fast Open requests than it was configured for. This only shows up with SO_REUSEPORT listener migration, where closing a listener hands its still-pending TFO children over to a surviving one. fastopenq.qlen is charged in tcp_fastopen_create_child() when the child is created and uncharged in reqsk_fastopen_remove() when the handshake completes. The uncharge follows rsk_listener of the request the child points at, and inet_reqsk_clone() has repointed the child at a new request owned by the new listener, so the ++ and the -- land on two different sockets. The new listener\u0026apos;s qlen drifts negative and its limit no longer binds. Charge the new listener during migration, like reqsk_queue_migrated() already does for queue-\u0026gt;young and queue-\u0026gt;qlen.(CVE-2026-74696)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp: fix potential use-after-free in tunnel segmentation\n\n__skb_udp_tunnel_segment() gets the UDP header before ensuring the\ntunnel header is in the skb head. If the pull reallocates skb-\u0026gt;head,\nthe saved UDP header pointer is no longer valid.\n\nGet the UDP header after the pull to avoid a potential use-after-free.(CVE-2026-74705)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u0026gt;netns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u0026gt;netns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u0026gt;netns_id (id)\n  read opts-\u0026gt;netns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.(CVE-2026-74715)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Preserve pointer state for commuted arithmetic\n\nWhen scalar += pointer is handled in adjust_ptr_min_max_vals(), the\ndestination register inherits the pointer state from the source pointer.\nCopying only selected fields is fragile because pointer provenance is\ntracked by several bpf_reg_state fields.\n\nUse the caller\u0026apos;s temporary offset register to preserve the scalar operand\nwhile replacing the destination with the full pointer state. This preserves\nthe frame number for PTR_TO_STACK registers and keeps parent identity\nfields consistent.(CVE-2026-74720)\n\nIn the Linux kernel, the following vulnerability has been resolved: ipvs: avoid out-of-bounds write in ip_vs_nat_icmp. Sashiko warns that a local attacker can modify the packet while it is processed by IPVS. Some places read the IP ihl field multiple times which can cause out-of-bounds access. One such place is ip_vs_nat_icmp where we can write after the validated area. Fix it by providing ciph argument just like it is done for IPv6 and use ciph-\u0026gt;len as offset to the embedded transport header. Modify some IPv4 header checks by reading the ihl field only once.(CVE-2026-74724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nbonding: alb: re-check primary_is_promisc under RTNL in bond_alb_monitor\\n\\nbond_alb_monitor() reads primary_is_promisc under RCU, then drops RCU and takes RTNL via rtnl_trylock() before undoing the promiscuity it set on the active slave. In that window the active slave can change under RTNL (RTM_DELLINK -\u0026gt; __bond_release_one() -\u0026gt; bond_alb_handle_active_change()), which already drops the promiscuity and clears primary_is_promisc. The monitor still acts on the stale decision: if the slave was removed with no failover, curr_active_slave is now NULL and the deref faults; if it failed over, the stale dev_set_promiscuity(-1) underflows the new slave\u0026apos;s promiscuity counter and pins it in IFF_PROMISC.\\n\\n  Oops: general protection fault, probably for non-canonical address ...\\n  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\\n  Workqueue: b42 bond_alb_monitor\\n  RIP: 0010:bond_alb_monitor (drivers/net/bonding/bond_alb.c:1600)\\n   process_one_work (kernel/workqueue.c:3322)\\n   worker_thread (kernel/workqueue.c:3486)\\n   kthread (kernel/kthread.c:436)\\n   ret_from_fork (arch/x86/kernel/process.c:158)\\n  Kernel panic - not syncing: Fatal exception\\n\\nRe-check primary_is_promisc (and curr_active_slave) after taking RTNL so the monitor only undoes an increment it still owns. The other bonding monitors already re-read state under RTNL in their commit phase (bond_miimon_commit/bond_ab_arp_commit); bond_alb_monitor() was the only one acting on the pre-trylock decision.(CVE-2026-74726)\n\nIn the Linux kernel, the following vulnerability has been resolved: NFS: Pin the \u0026apos;struct nfs_server\u0026apos; during a FREE_STATEID call. Dan Aloni reports that he was able to hit a use-after-free bug if a FREE_STATEID operation gets delayed for whatever reason. Fix this by bumping the refcount of the \u0026apos;struct nfs_server\u0026apos; object for the duration of the FREE_STATEID so it doesn\u0026apos;t get cleaned up from underneath us while operations are still in flight.(CVE-2026-74730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nfirewire: ohci: fix NULL pointer dereference in ar_context_release\\n\\nDuring the error handling path of the driver\u0026apos;s probe function, a NULL pointer dereference can occur in ar_context_release().\\n\\nWhen pci_probe() fails early (e.g., if pcim_enable_device() or MMIO mapping fails), the devres cleanup mechanism invokes release_ohci(). This function unconditionally calls ar_context_release() to clean up the asynchronous receive contexts. However, if ar_context_init() was not yet called, ctx-\u0026gt;ohci remains NULL (as the fw_ohci structure is zero-initialized by devres_alloc()).\\n\\nar_context_release() immediately dereferences ctx-\u0026gt;ohci to get the dev pointer before checking if the context was actually initialized, leading to a crash.(CVE-2026-74734)\n\nIn the Linux kernel, the following vulnerability has been resolved: net/sched: cls_u32: skip hash tables in u32_bind_class(). u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses \u0026amp;n-\u0026gt;res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res-\u0026gt;classid in tc_cls_bind_class().(CVE-2026-74739)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvlan: inherit needed_headroom and needed_tailroom from phy_dev\n\nipvlan devices inherit hard_header_len from phy_dev during ipvlan_init(),\nbut leave needed_headroom and needed_tailroom set to 0.\n\nWhen the underlying phy_dev (or stacked lower device) requires extra headroom\nor tailroom for headers/trailers (e.g. macsec, ipsec, wireguard, tunnels, or\nveth with rx headroom), upper layers calculating packet headroom and tailroom\nfail to reserve sufficient space.\n\nThis can result in reallocation overhead, skb headroom underflows, or KASAN\nslab-use-after-free crashes when dev_hard_header() / ipvlan_hard_header()\nprepends header data or when lower devices append tailroom.\n\nFix this by:\n1. Inheriting needed_headroom and needed_tailroom from phy_dev in ipvlan_init().\n2. Propagating needed_headroom and needed_tailroom updates to attached ipvlans\n   in ipvlan_device_event() when receiving NETDEV_FEAT_CHANGE events.(CVE-2026-74744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nipvs: revalidate ihl to prevent out-of-bounds access\\n\\nWhile the outer IP header is already pulled into the skb head,\\nwe must be careful and revalidate the embedded headers after\\nreading them from the skb frags to prevent out-of-bounds\\naccess.\\n\\nOne such place reported by Sashiko is ip_vs_nat_icmp() where\\nlocal process can change the ihl field and after\\nskb_ensure_writable() we can see larger value which is a\\nproblem for the ip_send_check(cih) calls.\\n\\nAdd check to drop the packet if the ihl field is changed.(CVE-2026-74747)\n\nIn the Linux kernel, the netfilter/ipset component has a refcount race condition vulnerability. __ip_set_put_byindex() resolved the index to a set pointer under RCU, then took ip_set_ref_lock in __ip_set_put() to decrement set-\u0026gt;ref. ip_set_swap() holds that same lock while swapping both the ip_set_list slots and the two sets\u0026apos; ref counters, so it can interleave between the dereference and the lock acquisition, leaving the caller to decrement a set whose reference already moved to the other index and hit BUG_ON(set-\u0026gt;ref == 0). list_set_gc() reaches this from timer softirq, which the nfnl mutex does not serialize against swap: an expiring list:set member calls list_set_del() -\u0026gt; ip_set_put_byindex() while IPSET_CMD_SWAP runs on the referenced sets. This vulnerability can cause kernel panic.(CVE-2026-74748)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Reject exited events as group leaders\n\nperf_event_remove_on_exec() sets remove-on-exec events to the EXIT state and detaches their group relationships. The event\u0026apos;s file descriptor can remain open, however, and perf_event_open() currently accepts that event as a group leader because its early validation rejects only REVOKED and DEAD events.\n\nA new sibling can consequently be linked to the detached leader. When the leader is closed, perf_group_detach() observes that its PERF_ATTACH_GROUP bit is already clear and skips the new sibling. The sibling then retains a group_leader pointer to the freed event.\n\nReject group leaders in the EXIT state. Perform the check while holding the shared context mutex so that an exec in the target task cannot detach the leader between validation and group attachment.\n\n[peterz: make the earlier test fully consistent](CVE-2026-74753)\n\nIn the Linux kernel, a deadlock vulnerability has been found in the ceph filesystem. A reader can hang forever in __ceph_get_caps() when the client no longer holds FILE_RD, but local cap state still says that the capability is already wanted (via mds_wanted). One way to trigger this is through MDS cap revocation. If another client performs a conflicting operation, the MDS can revoke FILE_RD from the reader; the next read then has to reacquire FILE_RD. If the cap update that should request FILE_RD never reaches the MDS after cap-\u0026gt;mds_wanted was raised, the reader is left holding only non-file caps while local mds_wanted still includes the file read caps, causing the reader to wait indefinitely.(CVE-2026-80527)\n\nIn the Linux kernel, the following vulnerability has been resolved: ceph: avoid fs reclaim while using current-\u0026gt;journal_info. handle_reply() stores a ceph_mds_request pointer in current-\u0026gt;journal_info while filling the inode and dentry cache from an MDS reply. An allocation in this section can enter direct reclaim and prune dentries from another filesystem. If this dirties an ext4 inode, ext4 starts a JBD2 transaction. JBD2 interprets the Ceph request in current-\u0026gt;journal_info as a journal handle and dereferences the request\u0026apos;s r_tid as h_transaction, causing a kernel crash.(CVE-2026-80528)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nxfs: don\u0026apos;t swallow dquot recovery verification errors\\n\\nxlog_recover_dquot_commit_pass2() validates the recovered dquot with xfs_dqblk_verify() and, on failure, sets error = -EFSCORRUPTED and jumps to out_release. But out_release unconditionally returns 0, so the corruption error is discarded: the caller xlog_recover_items_pass2() sees success, log recovery proceeds as if the dquot were valid, and the corrupt quota buffer can be written back to disk.(CVE-2026-80529)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: bounds-check buffer log item\u0026apos;s dirty bitmap\n\nxlog_recover_do_reg_buffer() replays each dirty region described by a\nbuffer log item\u0026apos;s bitmap into the buffer read for that item:\n\n\tmemcpy(xfs_buf_offset(bp, (uint)bit \u0026lt;\u0026lt; XFS_BLF_SHIFT),\n\t\titem-\u0026gt;ri_buf[i].iov_base,\n\t\tnbits \u0026lt;\u0026lt; XFS_BLF_SHIFT);\n\nThe destination offset (bit/nbits, from the logged dirty bitmap) and the\nbuffer size (from the logged blf_len) are both attacker-controlled and\notherwise unrelated, yet the only thing bounding the copy is an ASSERT(),\nwhich compiles away on production kernels. A crafted image logging a\nsmall blf_len together with a bitmap bit past the end of that buffer\ndrives the memcpy() past the buffer\u0026apos;s allocation, corrupting adjacent\nkernel heap during mount-time log recovery. This is reachable by anyone\nwho can get a crafted image mounted -- the malicious-filesystem threat\nmodel XFS already guards against elsewhere.\n\nTurn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery\nof the buffer with -EFSCORRUPTED, consistent with the validate-and-fail\nidiom already used in xlog_recover_do_inode_buffer() and\nxfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes\nSTATIC int and its three callers propagate the error.\n\nFound and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted\nimage trips a slab-out-of-bounds write before this change and fails\nrecovery cleanly with -EFSCORRUPTED after it.(CVE-2026-80536)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Move cp cleanup out of not operational\n\nThe fsm_notoper() routine is called when the device has been\nlost, and is (by definition) no longer operational. Since this\ncan happen asynchronously from the normal behavior of the\ndriver, the cleanup may happen when holding other locks\nin the calling sequence (notably, the cio subchannel lock).\n\nPush the cleanup of the private-\u0026gt;cp resources to a workqueue,\nwhere it can be done out from under that lock sequence and\na future patch can safely manage the locking requirements.(CVE-2026-80549)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Ensure first IDAW remains constant\n\nThe first IDAW in a list does not need to be on a 2K/4K boundary\nlike all others, and so is read separately to accurately calculate\nthe size of the buffer needed to read the full IDAL.\n\nVerify that the address found in the first IDAW is unchanged between\nreads, to ensure a consistent set of IDAWs being worked with.(CVE-2026-80551)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: fix OOB read in decode_watchers() via missing bounds check\n\nceph_start_decoding() validates that struct_len bytes remain in the\nbuffer after the encoding header, but accepts struct_len=0 as valid:\nceph_decode_need(p, end, 0, bad) always passes. When a malicious or\ncompromised OSD sends an obj_list_watch_response_t reply with\nstruct_len=0, ceph_start_decoding() returns success with p == end,\nleaving zero bytes guaranteed for subsequent reads.\n\nThe immediately following ceph_decode_32(p) in decode_watchers() has\nno preceding bounds check. With p == end this is a 4-byte read past\nthe validated buffer boundary. The garbage value is then passed\ndirectly to kzalloc_objs() as the watcher count.\n\nThe sibling function decode_watcher() already uses the safe variants\n(ceph_decode_copy_safe, ceph_decode_64_safe, ceph_decode_skip_32)\nafter its own ceph_start_decoding() call. decode_watchers() is the\nonly site that uses the bare variant, confirming an oversight.\n\nFix by replacing ceph_decode_32(p) with ceph_decode_32_safe(p, end,\n*num_watchers, bad), consistent with the established pattern.\n\nAttacker model: a malicious or compromised OSD in a multi-tenant Ceph\ndeployment (e.g. cloud) can trigger this against any kernel client\nthat calls CEPH_OSD_OP_LIST_WATCHERS, without any further privileges\nbeyond OSD session establishment.\n\n[ idryomov: trim changelog ](CVE-2026-80557)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: Avoid using invalid osd indices from primary_temp\n\nA corrupted osdmap received from a Ceph monitor or OSD may contain osd\nindices in its pg_temp, primary_temp, pg_upmap, and pg_upmap_items parts\nthat don\u0026apos;t exist, i.e., that are greater than max_osd or smaller than\nCEPH_HOMELESS_OSD (-1). These indices are used to create the up and\nacting set in ceph_pg_to_up_acting_osds(), called from calc_target().\nWhile most of these osd indices are checked, the one from primary_temp\nis not. Subsequently, this may lead to calc_target() returning this\n(potentially invalid) index as target osd for a (linger) request.\nBecause the osd_state, osd_weight, and osd_addr arrays only contain\nmax_osd entries (with indices 0 to max_osd -1), this leads to\nout-of-bounds accesses when trying to read values from these arrays.\n\nThis patch fixes the issue by adding a check to get_temp_osds(), so that\nonly valid osd indices from primary_temp are used, and it falls back to\nusing the primary from pg_temp or the up set if it is invalid.\n\n[ idryomov: changelog ](CVE-2026-80558)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenrisc: signal: do not restore privileged SR bits on sigreturn\n\nrestore_sigcontext() copies the whole supervision register (SR) from the\nsignal frame and only clears SPR_SR_SM before the value is reloaded into\nthe hardware SR (through ESR and l.rfe) on the return to user space.  All\nother SR bits are left under user control.\n\nAn unprivileged task can thus return from a signal handler through a\ncrafted sigframe that clears SPR_SR_DME.  With the data MMU disabled the\nCPU performs no translation or protection on data accesses, so the task\ngains read and write access to arbitrary physical memory, a local\nprivilege escalation.  SPR_SR_IME, SPR_SR_SUMRA, SPR_SR_LEE, SPR_SR_EPH\nand the cache-enable bits are exposed the same way.  The ptrace GPR regset\nalready refuses any change to SR for exactly this reason.\n\nRestore only the arithmetic flag bits (F, CY, OV) from the signal frame\nand take every privileged control bit from the SR the kernel saved on\nsignal entry.\n\nVerified with qemu-system-or1k -M or1k-sim: before this change an\nunprivileged PoC clears SPR_SR_DME in rt_sigreturn and writes a marker to\nphysical address 0x03000000 (beyond the kernel\u0026apos;s mem=32M); afterwards the\nsame PoC receives SIGSEGV and physical memory is unchanged.(CVE-2026-80560)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nmptcp: avoid combining some incoming suboptions\\n\\nSome MPTCP suboptions are mutually exclusive according to the RFC8684, but also because in different places, the code doesn\u0026apos;t expect some combinations to be present. That\u0026apos;s specially true for suboptions that would be present twice, but with different attributes.\\n\\nThe new restrictions are the same as the ones applied on the output side, with mptcp_write_options. The same rules can be reused with a small fix: an MP_FASTCLOSE can be used with a DSS when the sender picks this option [1], which is not the case on Linux.(CVE-2026-80587)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: stop the timeout timer when releasing a never added disk\n\ndisk_release() undoes blk_mq_init_allocated_queue() for a disk whose probe failed before add_disk(), but it only calls blk_mq_exit_queue(). Nothing there stops q-\u0026gt;timeout, and that timer rolls forward: it stays pending until it next expires, not until the last request completes. So if the driver issued any I/O before adding the disk, the request_queue is freed while still linked into a timer wheel bucket.\n\nCommit 6f8191fdf41d (\u0026quot;block: simplify disk shutdown\u0026quot;) dropped the blk_cleanup_queue() call that used to stop it. __del_gendisk() and blk_mq_destroy_queue() still do; only the probe failure path lost it.\n\nnvme gets there because nvme_update_ns_info() submits Report Zones or FDP io-mgmt-recv on ns-\u0026gt;queue before the disk is added, so a later failure - a concurrent reset setting NVME_CTRL_FROZEN, or device_add_disk() failing - lands in put_disk() with the timer armed, leading to a use-after-free condition.(CVE-2026-80589)\n\nIn the Linux kernel, the following vulnerability has been resolved: tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg. Sashiko found that user can cause this WARN_ON_ONCE() easily with adding a kprobe event based on a raw address with BTF parameter. Since this is not an unexpected condition, remove the WARN_ON_ONCE().(CVE-2026-80607)\n\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: processor_idle: Mark LPI enter functions as __cpuidle. When function tracing or Kprobes is enabled, entering an ACPI Low Power Idle (LPI) state triggers the following RCU splat: RCU not on for: acpi_idle_lpi_enter+0x4/0xd8. The acpi_idle_lpi_enter() function is invoked within the cpuidle path after RCU has already been disabled for the current local CPU. Consequently, ftrace\u0026apos;s function_trace_call() expects RCU to be actively watching before recording trace data, emitting a warning if it is not. Fix this by annotating acpi_idle_lpi_enter(), the generic __weak stub, and the RISC-V implementation of acpi_processor_ffh_lpi_enter() with __cpuidle. This moves these functions into the \u0026apos;.cpuidle.text\u0026apos; section, implicitly disabling ftrace instrumentation (notrace) along this sensitive path and preventing trace-induced RCU warnings during idle entry.(CVE-2026-80611)\n\nIn the Linux kernel, the netfilter synproxy module has an unaligned memory access issue in timestamp adjustment. Use get_unaligned_be32() and put_unaligned_be32() to safely read and write the timestamp fields. This prevents performance degradation due to unaligned memory access or even a crash on strict alignment architectures. This follows the implementation of timestamp parsing in the networking stack at tcp_parse_options() and synproxy_parse_options().(CVE-2026-80637)\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nRDMA/hns: Fix warning in poll cq direct mode\\n\\nCQs allocated by ib_alloc_cq() always have a comp_handler. Though\\nin direct mode this handler is never expected to be called, it\\nis still called when the driver is reset, triggering the following\\nWARN_ONCE():\\n\\nCall trace:\\nib_cq_completion_direct+0x38/0x60\\nhns_roce_cq_completion+0x54/0x90 (hns_roce_hw_v2]\\nhns_roce_handle_device_err+Ox1c8/0x340 [hns_roce_hw_v2]\\nhns_roce_hw_v2_uninit_instance.constprop.0+0x34/0x70 [hns_roce_hw_v2]\\nhns_roce_hw_v2_reset_notify+0xc4/0xe0 [hns_roce_hw_v2]\\nhclge_notify_roce_client+0x60/0xbc [hclge]\\nhclge_reset_rebuild+0x48/0x34c [hclge]\\nhclge_reset_subtask+0xcc/0xec [hclge]\\nhclge_reset_service_task+0x80/0x160 [hclge]\\nhclge_service_task+0x50/0x80 (hclge]\\nprocess_one_work+0x1cc/0x4d0\\nworker_thread+0x154/0x414\\nkthread+0x104/0x144\\nret_from_fork+0x10/0x18(CVE-2026-80647)\n\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: ensure no dangling hcon references in iso_conn. After iso_conn_del(), ISO sockets should not dereference the hcon any more. Currently, clearing iso_conn::hcon relies on iso_conn_del() releasing the last reference to the iso_conn. Simplify this by explicitly clearing conn-\u0026gt;hcon in iso_conn_del(), to avoid more complex reasoning on races about who holds the last reference.(CVE-2026-80721)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: gro: properly validate BIG TCP aggregation criteria\n\nWhen GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB),\nBIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP\n(with sufficient MAC header room to insert the temporary HBH jumbo header).\n\nHowever, commit b1a78b9b9886 (\u0026quot;net: add support for ipv4 big tcp\u0026quot;)\nloosened the check in skb_gro_receive(), leading to several issues:\n\n1. skb_gro_receive() checked skb_headroom(p) instead of the actual space\n   before the MAC header (p-\u0026gt;mac_header). Because skb_headroom(p) includes\n   mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check\n   with p-\u0026gt;mac_header \u0026lt; 8 bytes. When ipv6_gro_complete() inserts the\n   temporary HBH jumbo header, the memmove() starts before skb-\u0026gt;head,\n   causing an out-of-bounds write and wrapping skb-\u0026gt;mac_header.\n2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q /\n   ETH_P_8021AD) to aggregate beyond 64KB because\n   p-\u0026gt;protocol != ETH_P_IPV6 was true.\n3. It checked p-\u0026gt;encapsulation instead of NAPI_GRO_CB(skb)-\u0026gt;encap_mark,\n   allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate\n   beyond 64KB.\n\nFix skb_gro_receive() to strictly enforce:\n- NAPI_GRO_CB(skb)-\u0026gt;proto == IPPROTO_TCP\n- Not encapsulated (!NAPI_GRO_CB(skb)-\u0026gt;encap_mark \u0026amp;\u0026amp; !p-\u0026gt;encapsulation)\n- Protocol must be either ETH_P_IP or ETH_P_IPV6\n- If ETH_P_IPV6, p-\u0026gt;mac_header must be at least\n  sizeof(struct hop_jumbo_hdr)\n\nReturning -E2BIG from skb_gro_receive() ensures that packets which cannot\nbecome BIG TCP are cleanly flushed at \u0026lt;= 64KB and delivered intact without\ndropping.\n\nThis issue does not exist in mainline (7.0+) because the subsystem was\nrewritten in commit 81be30c1f5f2 (\u0026quot;net/ipv6: Drop HBH for BIG TCP on RX\nside\u0026quot;), making this fix relevant only for older stable branches like\n6.18.y.(CVE-2026-80725)","status":"published","published":"2026-09-14T16:33:35Z","modified":"2026-09-13T16:45:52.354731727Z","cvss":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L","level":"critical"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"OESA-2026-3987","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\nBluetooth: hci_conn: Fix null ptr deref in hci_abort_conn()\n\nhci_abort_conn() read hci_skb_event(hdev-\u0026gt;sent_cmd) when a connection\nwas pending, but hdev-\u0026gt;sent_cmd can be NULL while req_status is still\nHCI_REQ_PEND, leading to a NULL pointer dereference and a general\nprotection fault from the hci_rx_work() receive path.\n\nInstead of inspecting hdev-\u0026gt;sent_cmd, track the in-flight create\nconnection command with a new per-connection HCI_CONN_CREATE flag and\nroute all cancellation through hci_cancel_connect_sync(), which\ndispatches to a dedicated per-type cancel function. The create command\nis in exactly one of two states: still queued, or in flight. The cancel\nfunction holds cmd_sync_work_lock across the whole decision: the worker\ntakes this lock to dequeue every entry, so while it is held a queued\ncommand cannot start running and an in-flight command cannot complete\nand let the next command become pending. This keeps the flag test and\nhci_cmd_sync_cancel() atomic with respect to the worker, so a queued\ncommand is simply dequeued, and an in-flight command owned by this\nconnection is cancelled without the risk of cancelling an unrelated\ncommand that became pending in the meantime. CIS uses the same flag\nmechanism via HCI_CONN_CREATE_CIS but cannot be dequeued per-connection.\n\nhci_acl_create_conn_sync() and hci_le_create_conn_sync() clear\nHCI_CONN_CREATE after the create command completes, but the command\nstatus handler can free conn via hci_conn_del() (for example when the\ncontroller rejects the connection) while the worker is still blocked on\nthe connection complete event. Hold a reference on conn across the\ncreate command so the flag can be cleared without a use-after-free.(CVE-2026-64405)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse-uring: fix race between registration and connection abortion\n\nThis fixes this race:\n- thread a: io_uring_enter -\u0026gt; register sqe -\u0026gt;\n  fuse_uring_create_ring_ent -\u0026gt; allocate ent but doesn\u0026apos;t grab queue_ref\n  yet\n- thread b: fuse_conn_destroy() -\u0026gt; fuse_chan_abort() -\u0026gt;\n  fuse_uring_abort() is a no-op due to queue ref being 0\n- thread a: grabs the queue_ref, queue_ref is now 1, rest of\n  fuse_uring_do_register() logic executes\n- thread b: fuse_chan_abort() returns, fuse_chan_wait_aborted() now runs\n  and calls\n  \u0026quot;wait_event(ring-\u0026gt;stop_waitq, atomic_read(\u0026amp;ring-\u0026gt;queue_refs) == 0);\u0026quot;\nThe abort/unmount thread will hang indefinitely in unkillable state as\nnothing will decrement queue_refs or wake stop_waitq, and the ring,\nqueue, and ent are leaked.\n\nFix this by checking fch-\u0026gt;connected under fch-\u0026gt;lock after the created\nent has grabbed a ref count on the queue. This ensures that in the\nscenario above, it is guaranteed that we either release the queue ref\nand wake up stop_waitq (in case fuse_chan_wait_aborted() is already\nwaiting) in fuse_uring_do_register() when we detect !fch-\u0026gt;connected, or\nif the connection is aborted after the check, it is guaranteed that the\nasync teardown worker will be running in the background cleaning up ents\nand decrementing the ent\u0026apos;s ref on the queue, which will unblock the\neventual queue and ring teardown.(CVE-2026-68095)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: challenge ACK for non-exact RST in SYN-RECEIVED\n\nThe SYN-RECEIVED request-socket path in tcp_check_req() accepts an\nin-window RST without requiring SEG.SEQ to exactly match RCV.NXT.  A\nnon-exact RST therefore removes the request instead of eliciting a\nchallenge ACK.\n\nRFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in\nSYN-RECEIVED: an exact RST resets the connection, while a non-exact\nin-window RST must trigger a challenge ACK and be dropped.\n\nApply that check before the ACK-field validation, following the RFC\nsequence-number, RST, then ACK processing order.  Factor the per-netns\nchallenge ACK quota out of tcp_send_challenge_ack() so request sockets\ncan share it.  Use the request socket\u0026apos;s send_ack() callback and its own\nout-of-window ACK timestamp to send and rate-limit the response.(CVE-2026-68118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: serialize qdisc_rtab_list against concurrent get/put\n\nqdisc_get_rtab() and qdisc_put_rtab() mutate the process-global singly\nlinked list qdisc_rtab_list and a plain non-atomic \u0026apos;int refcnt\u0026apos; with no\nlock. This was only safe because every caller historically held the RTNL\nmutex, which serialized all rate-table lookups, inserts and frees.\n\nThat invariant no longer holds. cls_flower sets\nTCF_PROTO_OPS_DOIT_UNLOCKED, so tc_new_tfilter() keeps rtnl_held == false\nfor it and sets TCA_ACT_FLAGS_NO_RTNL. That flag propagates through\ntcf_exts_validate_ex() -\u0026gt; tcf_action_init() -\u0026gt; tcf_action_init_1() -\u0026gt;\ntcf_police_init(), which calls qdisc_get_rtab()/qdisc_put_rtab() with the\nRTNL mutex NOT held. Two RTM_NEWTFILTER requests on different CPUs, each\nadding a flower filter with a police action carrying the same rate, then\nrace on qdisc_rtab_list and on the non-atomic refcnt, leading to a\nuse-after-free / double-free of the kmalloc-2k struct qdisc_rate_table.\nqdisc_rtab_list is a single global (not per-netns), so the corrupted\nobject is shared system-wide.\n\n  BUG: KASAN: slab-use-after-free in qdisc_put_rtab+0x12f/0x160\n   qdisc_put_rtab+0x12f/0x160\n   tcf_police_init+0xda9/0x1590\n   tcf_action_init_1+0x460/0x6b0\n   tcf_action_init+0x439/0xa40\n   tcf_exts_validate_ex+0x42d/0x550\n   fl_change+0xddd/0x7da0\n   tc_new_tfilter+0xaa7/0x2420\n   rtnetlink_rcv_msg+0x95e/0xe90\n  which belongs to the cache kmalloc-2k of size 2048\n\nProtect qdisc_rtab_list and the refcount with a dedicated spinlock. The\n(sleeping, GFP_KERNEL) allocation in qdisc_get_rtab() is performed before\ntaking the lock; if a concurrent inserter added an identical table in the\nmeantime the freshly allocated one is freed under the lock, so no\nduplicate is leaked. qdisc_put_rtab() now decrements the refcount and\nunlinks under the same lock.(CVE-2026-68138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: fix out-of-bounds bitmap_set() with zero-length range\n\nifs_set_range_dirty() and ifs_set_range_uptodate() compute last_blk\nas (off + len - 1) \u0026gt;\u0026gt; i_blkbits.  When off is 0 and len is 0, the\nunsigned subtraction underflows to SIZE_MAX, producing a huge\nlast_blk and nr_blks value that causes bitmap_set() to write far\nbeyond the ifs-\u0026gt;state allocation.\n\nRegarding ifs_set_range_uptodate(), it is temporarily safe because len\ncannot be passed in as 0. However, for ifs_set_range_dirty() this is\nreachable from __iomap_write_end(): when copy_folio_from_iter_atomic()\nreturns 0 (e.g. user buffer fault) and the folio is already uptodate,\nthe guard at the top of __iomap_write_end() does not trigger because\n!folio_test_uptodate() is false, and iomap_set_range_dirty() is called\nwith copied == 0.\n\nAdd a !len guard to both functions before the computation, so that a\nzero-length range is a no-op.(CVE-2026-68145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndm-verity: fix buffer overflow in FEC calculation\n\nThere\u0026apos;s a buffer overflow in dm-verity-fec:\n\nif (neras \u0026amp;\u0026amp; *neras \u0026lt;= v-\u0026gt;fec-\u0026gt;roots)\n\tfio-\u0026gt;erasures[(*neras)++] = i;\n\nThis allows *neras to reach roots + 1 (the post-increment pushes it past\nroots). This value is then passed as no_eras to decode_rs8(). Inside the\nRS decoder (lib/reed_solomon/decode_rs.c:113-121), the erasure locator\npolynomial loop writes lambda[j] where j can reach nroots + 1 — one\nelement past the end of lambda[] (which is sized nroots + 1, valid\nindices 0..nroots). The out-of-bounds write lands on syn[0], corrupting\nthe syndrome buffer.(CVE-2026-72098)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: fix zone comparison in tuple dedup\n\nThe \u0026quot;already exists\u0026quot; dedup logic in __nf_conncount_add() decides\nwhether a connection has already been counted and can be skipped instead\nof incrementing the connlimit count.  It compares the conntrack zone of a\nlist entry with the zone of the connection being added using\nnf_ct_zone_id() and nf_ct_zone_equal(), passing conn-\u0026gt;zone.dir or\nzone-\u0026gt;dir as the direction argument.\n\nThose helpers take enum ip_conntrack_dir values: IP_CT_DIR_ORIGINAL is 0\nand IP_CT_DIR_REPLY is 1.  However, zone-\u0026gt;dir is a u8 bitmask:\nNF_CT_ZONE_DIR_ORIG is 1, NF_CT_ZONE_DIR_REPL is 2 and\nNF_CT_DEFAULT_ZONE_DIR is 3.  Passing that bitmask as the enum direction\nshifts the meaning of every non-zero value.  An ORIG-only zone passes 1\nand is tested as REPLY, while REPL-only and default zones pass 2 or 3 and\ntest bits beyond the valid direction range.  In those cases\nnf_ct_zone_id() can fall back to NF_CT_DEFAULT_ZONE_ID instead of using\nthe real zone id, so different zones can be treated as equal and dedup\ncollapses to tuple equality alone.\n\nnf_conncount stores and compares the original-direction tuple for a\nconnection.  If an skb already has an attached conntrack entry,\nget_ct_or_tuple_from_skb() explicitly copies\nct-\u0026gt;tuplehash[IP_CT_DIR_ORIGINAL].tuple, regardless of the packet\u0026apos;s\nctinfo.  Therefore the zone comparison in the tuple dedup path must use\nIP_CT_DIR_ORIGINAL as well; the zone direction bitmask describes where a\nzone id applies, not which direction this conncount tuple represents.\n\nFix the two dedup comparisons by passing IP_CT_DIR_ORIGINAL directly.\nDo not special-case NF_CT_DEFAULT_ZONE_DIR and do not compare raw zone\nids: using the existing helpers with IP_CT_DIR_ORIGINAL preserves the\ndirection-aware NF_CT_DEFAULT_ZONE_ID fallback.  A default bidirectional\nzone contains the ORIG bit, so it naturally returns the real zone id;\nreply-only zones continue to fall back for original-direction tuple\ncomparisons.(CVE-2026-72247)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix err_chunk memory leaks in INIT handling\n\nWhen sctp_verify_init() encounters unrecognized parameters, it allocates an\nerr_chunk to report them. However, this chunk is leaked in several code\npaths:\n\n1. In sctp_sf_do_5_1B_init(), if security_sctp_assoc_request() fails after\n   sctp_verify_init() has populated err_chunk, the function returns\n   immediately without freeing it.\n\n2. In sctp_sf_do_unexpected_init(), the same leak occurs on the\n   security_sctp_assoc_request() failure path.\n\n3. In sctp_sf_do_unexpected_init(), on the success path after copying\n   unrecognized parameters to the INIT-ACK, the function returns without\n   freeing err_chunk, unlike sctp_sf_do_5_1B_init() which properly frees\n   it.\n\nFix all three leaks by adding sctp_chunk_free(err_chunk) calls before\nreturning in the error paths and on the success path in\nsctp_sf_do_unexpected_init().(CVE-2026-72413)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid5: avoid R5_Overlap races while breaking stripe batches\n\nKCSAN report a race in break_stripe_batch_list() vs. raid5_make_request()\non sh-\u0026gt;dev[i].flags (plain word write vs. atomic bit op)..\n\nand .. one possible scenario is:\n\nCPU1                            CPU2\nbreak_stripe_batch_list(sh1)\n-\u0026gt; handle sh2\n-\u0026gt; lock(sh2)\n-\u0026gt; sh2-\u0026gt;batch_head = NULL\n-\u0026gt; unlock(sh2)\n-\u0026gt; test_and_clear_bit(R5_Overlap, sh2-\u0026gt;dev[i].flags)\n-\u0026gt; wake_up_bit(sh2-\u0026gt;dev[i].flags)\n                                raid5_make_request()\n                                -\u0026gt; add_all_stripe_bios(sh2)\n                                -\u0026gt; lock(sh2)\n                                -\u0026gt; stripe_bio_overlaps(sh2) returns true\n\t\t\t\t   batch_head is NULL, so new bio overlap\n\t\t\t\t   exist bio on sh2 -\u0026gt; true\n                                -\u0026gt; set_bit(R5_Overlap, sh2-\u0026gt;dev[i].flags)\n                                -\u0026gt; unlock(sh2)\n                                -\u0026gt; wait_on_bit(sh2-\u0026gt;dev[i].flags)\n-\u0026gt; sh2-\u0026gt;dev[i].flags = sh1-\u0026gt;dev[i].flags \u0026amp; ~R5_Overlap\n\nNo wait_up_bit(), CPU2 could be wait_on_bit() forever...\n\nFix by :\n- Expand the protect zone.\n- Use batch_head\u0026apos;s device flag\u0026apos;s snaphot when no held head_sh-\u0026gt;stripe_lock.\n- Move sh/head_sh-\u0026gt;batch_head = NULL to the end of protected zone , and ,\n  any concurrent add_all_stripe_bios() grabs sh-\u0026gt;stripe_lock now either:\n\t- see batch_head != null, and , is rejected by stripe_bio_overlaps()\n\t  under the lock (no R5_Overlap wait ) , or ,\n\t- sees batch_head == NULL, only after dev[i].flags has already been\n\t  set and the prior R5_Overlap waiters worken.\n\nKCSAN report:\n================================================\n  BUG: KCSAN: data-race in break_stripe_batch_list / raid5_make_request\n\n  write (marked) to 0xffff8e89c8117548 of 8 bytes by task 4042 on cpu 0:\n    raid5_make_request+0xea0/0x2930\n    md_handle_request+0x4a2/0xa40\n    md_submit_bio+0x109/0x1a0\n    __submit_bio+0x2ec/0x390\n    submit_bio_noacct_nocheck+0x457/0x710\n    submit_bio_noacct+0x2a7/0xc20\n    submit_bio+0x56/0x250\n    blkdev_direct_IO+0x54c/0xda0\n    blkdev_write_iter+0x38f/0x570\n    aio_write+0x22b/0x490\n    io_submit_one+0xa51/0xf70\n    __x64_sys_io_submit+0xf7/0x220\n    x64_sys_call+0x1907/0x1c60\n    do_syscall_64+0x130/0x570\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\n  read to 0xffff8e89c8117548 of 8 bytes by task 4010 on cpu 5:\n    break_stripe_batch_list+0x249/0x480\n    handle_stripe_clean_event+0x720/0x9b0\n    handle_stripe+0x32fb/0x4500\n    handle_active_stripes.isra.0+0x6e0/0xa50\n    raid5d+0x7e0/0xba0\n    md_thread+0x15a/0x2d0\n    kthread+0x1e3/0x220\n    ret_from_fork+0x37a/0x410\n    ret_from_fork_asm+0x1a/0x30\n\n  value changed: 0x0000000000000019 -\u0026gt; 0x0000000000000099 --\u0026gt; R5_Overlap(CVE-2026-72420)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/bnxt_re: Proper rollback if the ioremap fails\n\nbnxt_qplib_alloc_dpi returns success even if ioremap fails.\nAdd the proper rollback when the ioremap fails and return\n-ENOMEM status.(CVE-2026-72496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: clear sock_ops cb flags before force-closing a child socket\n\nA child socket inherits the listener\u0026apos;s bpf_sock_ops_cb_flags via\nsk_clone_lock(). If its setup fails in tcp_v4_syn_recv_sock() /\ntcp_v6_syn_recv_sock(), the child is freed through put_and_exit, where\ninet_csk_prepare_forced_close() drops the socket lock and tcp_done() runs\nwithout it.\n\nIf BPF_SOCK_OPS_STATE_CB_FLAG was inherited, tcp_done() -\u0026gt; tcp_set_state()\ncalls tcp_call_bpf(), which expects the lock and trips sock_owned_by_me():\n\n  WARNING: include/net/sock.h:1799 at tcp_set_state+0x433/0x550\n  RIP: 0010:tcp_set_state+0x433/0x550 include/net/sock.h:1799\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_done+0xba/0x250 net/ipv4/tcp.c:5095\n   tcp_v4_syn_recv_sock+0x850/0xa50 net/ipv4/tcp_ipv4.c:1787\n   tcp_check_req+0xf30/0x1360 net/ipv4/tcp_minisocks.c:926\n   tcp_v4_rcv+0x1047/0x1b50 net/ipv4/tcp_ipv4.c:2164\n   \u0026lt;/IRQ\u0026gt;\n\nThe child is freed before it is ever established, so it should run no\nsock_ops callback. Clear its cb flags in inet_csk_prepare_for_destroy_sock(),\nthe common point for the IPv4, IPv6 and chtls forced-close paths and for the\nMPTCP -\u0026gt;syn_recv_sock() failure path (dispose_child), which reaches tcp_done()\non a child that was never established too.(CVE-2026-74268)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: fib: Don\u0026apos;t dump dying fib_info in fib_leaf_notify().\n\nsyzbot reported use-after-free in nsim_fib4_prepare_event(). [0]\n\nThe problem is that the following functions call fib_info_hold() /\nrefcount_inc() while dumping fib_info under RCU, which is unsafe.\n\n  * mlxsw_sp_router_fib4_event()\n  * rocker_router_fib_event()\n  * nsim_fib4_prepare_event()\n\nrefcount_inc_not_zero() must be used, but it would be too late\nthere.\n\nLet\u0026apos;s guarantee the lifetime of fib_info in fib_leaf_notify().\n\nNote that IPv6 does not need the corresponding change since\nfib6_table_dump() holds fib6_table.tb6_lock.\n\n[0]:\nrefcount_t: addition on 0; use-after-free.\nWARNING: lib/refcount.c:25 at refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25, CPU#0: kworker/u8:15/3420\nModules linked in:\nCPU: 0 UID: 0 PID: 3420 Comm: kworker/u8:15 Not tainted syzkaller #0 PREEMPT_{RT,(full)}\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026\nWorkqueue: netns cleanup_net\nRIP: 0010:refcount_warn_saturate+0x9f/0x110 lib/refcount.c:25\nCode: eb 66 85 db 74 3e 83 fb 01 75 4c e8 1b f1 22 fd 48 8d 3d 84 cb f1 0a 67 48 0f b9 3a eb 4a e8 08 f1 22 fd 48 8d 3d 81 cb f1 0a \u0026lt;67\u0026gt; 48 0f b9 3a eb 37 e8 f5 f0 22 fd 48 8d 3d 7e cb f1 0a 67 48 0f\nRSP: 0018:ffffc9000f2c7270 EFLAGS: 00010293\nRAX: ffffffff84a18858 RBX: 0000000000000002 RCX: ffff888032ff9ec0\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8f9353e0\nRBP: 0000000000000000 R08: ffff888032ff9ec0 R09: 0000000000000005\nR10: 0000000000000100 R11: 0000000000000004 R12: ffff8880570cc000\nR13: dffffc0000000000 R14: ffff88802b40563c R15: ffff8880570cc000\nFS:  0000000000000000(0000) GS:ffff888126173000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fb1f4d5d000 CR3: 000000006072a000 CR4: 00000000003526f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __refcount_add include/linux/refcount.h:-1 [inline]\n __refcount_inc include/linux/refcount.h:366 [inline]\n refcount_inc include/linux/refcount.h:383 [inline]\n fib_info_hold include/net/ip_fib.h:629 [inline]\n nsim_fib4_prepare_event drivers/net/netdevsim/fib.c:930 [inline]\n nsim_fib_event_schedule_work drivers/net/netdevsim/fib.c:1000 [inline]\n nsim_fib_event_nb+0x1055/0x1240 drivers/net/netdevsim/fib.c:1043\n call_fib_notifier+0x45/0x80 net/core/fib_notifier.c:25\n call_fib_entry_notifier net/ipv4/fib_trie.c:90 [inline]\n fib_leaf_notify net/ipv4/fib_trie.c:2176 [inline]\n fib_table_notify net/ipv4/fib_trie.c:2194 [inline]\n fib_notify+0x36b/0x5e0 net/ipv4/fib_trie.c:2217\n fib_net_dump net/core/fib_notifier.c:70 [inline]\n register_fib_notifier+0x184/0x360 net/core/fib_notifier.c:108\n nsim_fib_create+0x85d/0x9f0 drivers/net/netdevsim/fib.c:1596\n nsim_dev_reload_create drivers/net/netdevsim/dev.c:1604 [inline]\n nsim_dev_reload_up+0x374/0x7c0 drivers/net/netdevsim/dev.c:1058\n devlink_reload+0x501/0x8d0 net/devlink/dev.c:475\n devlink_pernet_pre_exit+0x1ff/0x420 net/devlink/core.c:558\n ops_pre_exit_list net/core/net_namespace.c:161 [inline]\n ops_undo_list+0x187/0x940 net/core/net_namespace.c:234\n cleanup_net+0x56e/0x800 net/core/net_namespace.c:702\n process_one_work kernel/workqueue.c:3314 [inline]\n process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397\n worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478\n kthread+0x388/0x470 kernel/kthread.c:436\n ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;(CVE-2026-74289)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvhost: fix vhost_get_avail_idx for a non empty ring\n\nvhost_get_avail_idx is supposed to report whether it has updated\nvq-\u0026gt;avail_idx. Instead, it returns whether all entries have been\nconsumed, which is usually the same. But not always - in\ndrivers/vhost/net.c and when mergeable buffers have been enabled, the\ndriver checks whether the combined entries are big enough to store an\nincoming packet. If not, the driver re-enables notifications with\navailable entries still in the ring. The incorrect return value from\nvhost_get_avail_idx propagates through vhost_enable_notify and causes\nthe host to livelock if the guest is not making progress, as vhost will\nimmediately disable notifications and retry using the available entries.\n\nThis goes back to commit d3bb267bbdcb (\u0026quot;vhost: cache avail index in\nvhost_enable_notify()\u0026quot;) which changed vhost_enable_notify() to compare\nthe freshly read avail index against vq-\u0026gt;last_avail_idx instead of the\npreviously cached vq-\u0026gt;avail_idx. Commit 7ad472397667 (\u0026quot;vhost: move\nsmp_rmb() into vhost_get_avail_idx()\u0026quot;) then carried over the same\ncomparison when refactoring vhost_enable_notify() to call the unified\nvhost_get_avail_idx().\n\nThe obvious fix is to make vhost_get_avail_idx do what the comment\nsays it does and report whether new entries have been added.(CVE-2026-74356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1,raid10: fix deadlock in read error recovery path\n\nraid1d and raid10d may resubmit a split md cloned bio while handling\na read error. In this case, resubmitting the bio can lead to a deadlock\nif the array is suspended before md_handle_request() acquires an\nactive_io reference via percpu_ref_tryget_live().\n\nSince the cloned bio already holds an active_io reference,\ntrying to acquire another reference via percpu_ref_tryget_live()\ncan lead to a deadlock while the array is suspended.\n\nFix this by using percpu_ref_get() for md cloned bios.(CVE-2026-74375)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: Fix advertising data UAFs\n\nhci_find_adv_instance() returns an adv_info pointer that is valid only\nwhile hdev-\u0026gt;lock is held.  The advertising command-sync paths perform\ninstance lookups without that lock and, in some cases, retain the pointer\nwhile waiting for a controller response.\n\nAn advertising termination event can therefore interleave as follows:\n\n  hci_cmd_sync_work                 hci_rx_work\n  hci_find_adv_instance()\n  __hci_cmd_sync_status()\n    wait for controller reply       hci_dev_lock()\n                                    hci_remove_adv_instance()\n                                      kfree(adv)\n  adv-\u0026gt;scan_rsp_changed = false\n\nKASAN reported:\n\n  BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300\n  Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88\n  Workqueue: hci0 hci_cmd_sync_work\n  Call Trace:\n   hci_set_ext_scan_rsp_data_sync+0x2e1/0x300\n   hci_schedule_adv_instance_sync+0x390/0x4c0\n   hci_cmd_sync_work+0x173/0x300\n  Allocated by task 87:\n   hci_add_adv_instance+0x538/0xac0\n   add_advertising+0x885/0x1160\n  Freed by task 89:\n   kfree+0x131/0x3c0\n   hci_remove_adv_instance+0x1d8/0x3b0\n   hci_le_ext_adv_term_evt+0x17b/0x730\n\nProtect the instance lookup and payload construction in the extended\nadvertising, scan response, and periodic advertising data paths.  Snapshot\nthe advertising parameters under hdev-\u0026gt;lock, but release the lock before\nwaiting for the controller.\n\nClear advertising-data dirty bits before issuing their commands and\nrestore them after a failure using a fresh lookup.  Likewise, update the\nreported transmit power through a fresh lookup after the parameter command\ncompletes.  No adv_info pointer then survives an HCI command wait.(CVE-2026-74509)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/iommufd: Fix IOPF group ownership UAF\n\niopf_group_alloc() links each last-page IOPF group into the generic IOPF\npending list before invoking the domain fault handler.\niommufd_fault_iopf_handler() also queued an accepted group in the\nIOMMUFD deliver list without removing it from the generic pending list.\n\nWhen detach or HWPT replacement drops the device\u0026apos;s IOPF reference count\nto zero, an IOMMU driver may call iopf_queue_remove_device(). That\nfunction responds to and frees groups through the generic pending list\nwithout removing the same groups from IOMMUFD\u0026apos;s deliver list or response\nxarray. A later read, response, or cleanup can then access the freed\ngroup and cause a UAF.\n\nFix this by dequeuing an accepted group from the generic pending list\nbefore IOMMUFD queues it for userspace response.\nMake iopf_group_response() send a response regardless of pending-list\nmembership, so the dequeued group can still be completed by IOMMUFD.(CVE-2026-74520)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()\n\nsyzbot reported a memory leak [1] in the UDP tunnel NIC offload code.\n\nWhen device registration fails (e.g. in register_netdevice()), netdev core\nunwinds by sending a single NETDEV_UNREGISTER notification. If work was queued\nduring NETDEV_REGISTER (utn-\u0026gt;work_pending is set), udp_tunnel_nic_unregister()\nreturns early:\n\n\tif (utn-\u0026gt;work_pending)\n\t\treturn;\n\nBecause failed registrations do not enter netdev_wait_allrefs_any(), no\nsubsequent NETDEV_UNREGISTER rebroadcast will ever occur. As a result, the\nstruct udp_tunnel_nic allocated in udp_tunnel_nic_alloc() is leaked\npermanently.\n\nFix this by removing the early return. Instead, synchronously cancel any\npending work with cancel_delayed_work_sync() before freeing @utn.\n\nTo be able to call cancel_delayed_work_sync() while holding RTNL (the work also\nneeds RTNL), switch udp_tunnel_nic_device_sync_work() to rtnl_trylock(). If RTNL\nis contended, requeue the work with a 1 jiffy delay (via queue_delayed_work())\nto prevent high CPU contention while waiting for RTNL lock.\n\nThe utn-\u0026gt;work_pending bookkeeping is no longer needed and is removed, as\nthe workqueue core already tracks the pending/running state of the work.\n\n[1]\nBUG: memory leak\nunreferenced object 0xffff888127d5f840 (size 96):\n  comm \u0026quot;syz-executor\u0026quot;, pid 5806, jiffies 4294942188\n  backtrace (crc 99fdb6c8):\n    __kmalloc_noprof+0x3bf/0x550\n    udp_tunnel_nic_alloc net/ipv4/udp_tunnel_nic.c:756 [inline]\n    udp_tunnel_nic_register net/ipv4/udp_tunnel_nic.c:833 [inline]\n    udp_tunnel_nic_netdevice_event+0x804/0xab0 net/ipv4/udp_tunnel_nic.c:931\n    notifier_call_chain+0x59/0x160 kernel/notifier.c:85\n    call_netdevice_notifiers_info+0x7d/0xb0 net/core/dev.c:2250\n    register_netdevice+0xc10/0xeb0 net/core/dev.c:11478(CVE-2026-74543)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: validate offshift to prevent shift-out-of-bounds\n\nu32_change() copies the user-provided tc_u32_sel.offshift (unsigned char,\n0-255) into the kernel knode object without bounds validation. When a\npacket later hits u32_classify() with TC_U32_VAROFFSET set, it evaluates\n`ntohs(offmask \u0026amp; *data) \u0026gt;\u0026gt; offshift` where the left operand is a 16-bit\nvalue promoted to a 32-bit int. Any offshift \u0026gt;= 32 is undefined behavior\nper C11 6.5.7p3, triggerable by an unprivileged user via user/network\nnamespaces.\n\nUBSAN: shift-out-of-bounds in net/sched/cls_u32.c:236:43\nshift exponent 32 is too large for 32-bit type int\n\nFix this by rejecting offshift \u0026gt;= 16 during filter creation in\nu32_change().(CVE-2026-74544)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: make nft_object rhltable per table\n\nThe nft_object rhltable is global, this allows for accessing objects\nthat are being dismangled from lookup path by other existing netns.\nGiven the nft_obj_destroy() releases the object inmediately, this might\nlead to use-after-free of these objects that are being released.\nMake the existing rhltable per table to address this issue to deal with\nwith the nft_rcv_nl_event() path too.\n\nUpdate nft_obj_lookup() to take the table as non-const, otherwise,\ncompiler complains when passing the objname_ht to rhltable_lookup().(CVE-2026-74565)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\neventfs: Use children field for rcu head and add memory barriers\n\nWhen an eventfs inode is freed, it sets ei-\u0026gt;is_freed and then uses its\nei-\u0026gt;list to add it to the srcu link list as the list field is a union with\nthe rcu list head. As the ei-\u0026gt;list is used to iterate over an SRCU\nprotected list without taking the eventfs_mutex, there\u0026apos;s nothing stopping\nthe iteration over that list to see the ei-\u0026gt;rcu instead of the ei-\u0026gt;list\nand it will read a corrupt target.\n\nTo fix this, change the union of the rcu list head with the children list.\nOn freeing the eventfs inode, set the is_free and execute a smp_wmb()\nbefore adding the eventfs inode to the SRCU list.\n\nOn iteration of the ei-\u0026gt;children list, at the start, execute a smp_rmb()\nand then read the is_freed of the ei to see if the children list is still\nvalid. If is_freed is set, then the ei_child read is not valid and the\nloop should exit immediately.(CVE-2026-74605)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npacket: use consistent hard_header_len in TX_RING send path\n\ntpacket_snd() reads dev-\u0026gt;hard_header_len independently for skb\nallocation and header construction in tpacket_fill_skb(). Concurrent\nnetdevice reconfiguration can therefore make the reserved headroom\nsmaller than the amount later pushed, or make copylen - hard_header_len\nnegative.\n\nSnapshot hard_header_len once before processing ring frames and use it\nfor the frame limit, headroom allocation, copy length, and skb\nconstruction. Pass the snapshot to tpacket_fill_skb().\n\nThe separate SOCK_DGRAM consistency problem between hard_header_len and\nheader_ops-\u0026gt;create is not addressed here.(CVE-2026-74668)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u0026gt;netns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u0026gt;netns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u0026gt;netns_id (id)\n  read opts-\u0026gt;netns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.(CVE-2026-74715)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: avoid out-of-bounds write in ip_vs_nat_icmp\n\nSashiko warns that local attacker can modify the packet\nwhile it is processed by IPVS. Some places read the\nIP ihl field multiple times which can cause out-of-bounds\naccess. One such place is ip_vs_nat_icmp where we\ncan write after the validated area.\n\nFix it by providing ciph argument just like it is done for\nIPv6 and use ciph-\u0026gt;len as offset to the embedded transport\nheader.\n\nModify some IPv4 header checks by reading the ihl field\nonly once.(CVE-2026-74724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Pin the \u0026apos;struct nfs_server\u0026apos; during a FREE_STATEID call\n\nDan Aloni reports that he was able to hit a use-after-free bug if a\nFREE_STATEID operation gets delayed for whatever reason. Fix this by\nbumping the refcount of the \u0026apos;struct nfs_server\u0026apos; object for the duration\nof the FREE_STATEID so it doesn\u0026apos;t get cleaned up from underneath us\nwhile operations are still in flight.(CVE-2026-74730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfirewire: ohci: fix NULL pointer dereference in ar_context_release\n\nDuring the error handling path of the driver\u0026apos;s probe function, a NULL\npointer dereference can occur in ar_context_release().\n\nWhen pci_probe() fails early (e.g., if pcim_enable_device() or MMIO mapping\nfails), the devres cleanup mechanism invokes release_ohci(). This function\nunconditionally calls ar_context_release() to clean up the asynchronous\nreceive contexts. However, if ar_context_init() was not yet called,\nctx-\u0026gt;ohci remains NULL (as the fw_ohci structure is zero-initialized by\ndevres_alloc()).\n\nar_context_release() immediately dereferences ctx-\u0026gt;ohci to get the dev\npointer before checking if the context was actually initialized, leading to\na crash:\n\nOops: general protection fault, probably for non-canonical address\n0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI\nKASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]\nRIP: 0010:ar_context_release+0x3f/0x380 drivers/firewire/ohci.c:543\nCall Trace:\n release_ohci+0x3f/0x60 drivers/firewire/ohci.c:3567\n release_nodes drivers/base/devres.c:546 [inline]\n devres_release_all+0x1a8/0x260 drivers/base/devres.c:576\n device_unbind_cleanup drivers/base/dd.c:597 [inline]\n really_probe+0x451/0xae0 drivers/base/dd.c:772\n\nTo fix this, move the assignment of the dev pointer after the !ctx-\u0026gt;buffer\ncheck. If ctx-\u0026gt;buffer is NULL, it indicates that the context was never\nsuccessfully initialized and there is nothing to release, safely avoiding\nthe dereference of the uninitialized ctx-\u0026gt;ohci pointer.(CVE-2026-74734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvs: revalidate ihl to prevent out-of-bounds access\n\nWhile the outer IP header is already pulled into the skb head,\nwe must be careful and revalidate the embedded headers after\nreading them from the skb frags to prevent out-of-bounds\naccess.\n\nOne such place reported by Sashiko is ip_vs_nat_icmp() where\nlocal process can change the ihl field and after\nskb_ensure_writable() we can see larger value which is a\nproblem for the ip_send_check(cih) calls.\n\nAdd check to drop the packet if the ihl field is changed.(CVE-2026-74747)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: bounds-check buffer log item\u0026apos;s dirty bitmap\n\nxlog_recover_do_reg_buffer() replays each dirty region described by a\nbuffer log item\u0026apos;s bitmap into the buffer read for that item:\n\n\tmemcpy(xfs_buf_offset(bp, (uint)bit \u0026lt;\u0026lt; XFS_BLF_SHIFT),\n\t\titem-\u0026gt;ri_buf[i].iov_base,\n\t\tnbits \u0026lt;\u0026lt; XFS_BLF_SHIFT);\n\nThe destination offset (bit/nbits, from the logged dirty bitmap) and the\nbuffer size (from the logged blf_len) are both attacker-controlled and\notherwise unrelated, yet the only thing bounding the copy is an ASSERT(),\nwhich compiles away on production kernels. A crafted image logging a\nsmall blf_len together with a bitmap bit past the end of that buffer\ndrives the memcpy() past the buffer\u0026apos;s allocation, corrupting adjacent\nkernel heap during mount-time log recovery. This is reachable by anyone\nwho can get a crafted image mounted -- the malicious-filesystem threat\nmodel XFS already guards against elsewhere.\n\nTurn the ASSERT() into a real XFS_IS_CORRUPT() check that aborts recovery\nof the buffer with -EFSCORRUPTED, consistent with the validate-and-fail\nidiom already used in xlog_recover_do_inode_buffer() and\nxfs_dquot_item_recover.c. xlog_recover_do_reg_buffer() therefore becomes\nSTATIC int and its three callers propagate the error.\n\nFound and confirmed with KASAN on a CONFIG_XFS_DEBUG=n build: the crafted\nimage trips a slab-out-of-bounds write before this change and fails\nrecovery cleanly with -EFSCORRUPTED after it.(CVE-2026-80536)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Move cp cleanup out of not operational\n\nThe fsm_notoper() routine is called when the device has been\nlost, and is (by definition) no longer operational. Since this\ncan happen asynchronously from the normal behavior of the\ndriver, the cleanup may happen when holding other locks\nin the calling sequence (notably, the cio subchannel lock).\n\nPush the cleanup of the private-\u0026gt;cp resources to a workqueue,\nwhere it can be done out from under that lock sequence and\na future patch can safely manage the locking requirements.(CVE-2026-80549)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Ensure first IDAW remains constant\n\nThe first IDAW in a list does not need to be on a 2K/4K boundary\nlike all others, and so is read separately to accurately calculate\nthe size of the buffer needed to read the full IDAL.\n\nVerify that the address found in the first IDAW is unchanged between\nreads, to ensure a consistent set of IDAWs being worked with.(CVE-2026-80551)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenrisc: signal: do not restore privileged SR bits on sigreturn\n\nrestore_sigcontext() copies the whole supervision register (SR) from the\nsignal frame and only clears SPR_SR_SM before the value is reloaded into\nthe hardware SR (through ESR and l.rfe) on the return to user space.  All\nother SR bits are left under user control.\n\nAn unprivileged task can thus return from a signal handler through a\ncrafted sigframe that clears SPR_SR_DME.  With the data MMU disabled the\nCPU performs no translation or protection on data accesses, so the task\ngains read and write access to arbitrary physical memory, a local\nprivilege escalation.  SPR_SR_IME, SPR_SR_SUMRA, SPR_SR_LEE, SPR_SR_EPH\nand the cache-enable bits are exposed the same way.  The ptrace GPR regset\nalready refuses any change to SR for exactly this reason.\n\nRestore only the arithmetic flag bits (F, CY, OV) from the signal frame\nand take every privileged control bit from the SR the kernel saved on\nsignal entry.\n\nVerified with qemu-system-or1k -M or1k-sim: before this change an\nunprivileged PoC clears SPR_SR_DME in rt_sigreturn and writes a marker to\nphysical address 0x03000000 (beyond the kernel\u0026apos;s mem=32M); afterwards the\nsame PoC receives SIGSEGV and physical memory is unchanged.(CVE-2026-80560)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: processor_idle: Mark LPI enter functions as __cpuidle\n\nWhen function tracing or Kprobes is enabled, entering an ACPI Low\nPower Idle (LPI) state triggers the following RCU splat:\n\n  RCU not on for: acpi_idle_lpi_enter+0x4/0xd8\n  WARNING: CPU: 8 PID: 0 at include/linux/trace_recursion.h:162 function_trace_call+0x1e8/0x228\n\nThe acpi_idle_lpi_enter() function is invoked within the cpuidle\npath after RCU has already been disabled for the current local CPU.\nConsequently, ftrace\u0026apos;s function_trace_call() expects RCU to be\nactively watching before recording trace data, emitting a warning\nif it is not.\n\nFix this by annotating acpi_idle_lpi_enter(), the generic __weak\nstub, and the RISC-V implementation of acpi_processor_ffh_lpi_enter()\nwith __cpuidle. This moves these functions into the \u0026apos;.cpuidle.text\u0026apos;\nsection, implicitly disabling ftrace instrumentation (notrace) along\nthis sensitive path and preventing trace-induced RCU warnings during\nidle entry.(CVE-2026-80611)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: synproxy: fix unaligned memory access in timestamp adjustment\n\nUse get_unaligned_be32() and put_unaligned_be32() to safely read and\nwrite the timestamp fields. This prevents performance degradation due to\nunaligned memory access or even a crash on strict alignment\narchitectures.\n\nThis follows the implementation of timestamp parsing in the networking\nstack at tcp_parse_options() and synproxy_parse_options().(CVE-2026-80637)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: ISO: ensure no dangling hcon references in iso_conn\n\nAfter iso_conn_del(), ISO sockets should not dereference the hcon any\nmore.  Currently, clearing iso_conn::hcon relies on iso_conn_del()\nreleasing the last reference to the iso_conn.\n\nSimplify this by explicitly clearing conn-\u0026gt;hcon in iso_conn_del(), to\navoid more complex reasoning on races about who holds the last\nreference.(CVE-2026-80721)","status":"published","published":"2026-09-20T13:23:52Z","modified":"2026-09-20T13:30:32.806002034Z","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:47.643553Z"},{"id":"UBUNTU-CVE-2026-74715","description":"In the Linux kernel, the following vulnerability has been resolved: bpf: Fix netns reference imbalance in conntrack kfuncs The opts argument of the BPF conntrack kfuncs can point to a shared map value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read opts-\u003enetns_id separately when acquiring and releasing the network namespace reference. The reference imbalance can occur as follows:   CPU 0                                  CPU 1   read opts-\u003enetns_id (-1)   skip get_net_ns_by_id()                                          write opts-\u003enetns_id (id)   read opts-\u003enetns_id (id)   put_net(net) /* no matching get */ The reverse transition leaks the reference.  Repeating the unmatched put can destroy a live namespace and crash later users. The kernel reported:   Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]   RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700   Call Trace:    __sys_bpf+0x1662/0x50c0    __x64_sys_bpf+0x73/0xb0    do_syscall_64+0xf9/0x540    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception Snapshot every input field of opts with READ_ONCE() before validating or using it.  The netns_id snapshot keeps the namespace get/put pair balanced, while the other snapshots keep the remaining options from changing partway through an invocation.  The individual reads can still observe an inconsistent combination during a concurrent update, but each selected field value remains stable for that invocation.","status":"published","published":"2026-08-22T16:16:00Z","modified":"2026-11-10T02:51:40.111435636Z","cvss":[{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"},{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-10T03:20:25.726809Z"},{"id":"AZL-97341","title":"CVE-2026-74715 affecting package kernel for versions less than 6.6.161.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix netns reference imbalance in conntrack kfuncs\n\nThe opts argument of the BPF conntrack kfuncs can point to a shared\nmap value.  __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read\nopts-\u003enetns_id separately when acquiring and releasing the network\nnamespace reference.\n\nThe reference imbalance can occur as follows:\n\n  CPU 0                                  CPU 1\n  read opts-\u003enetns_id (-1)\n  skip get_net_ns_by_id()\n                                         write opts-\u003enetns_id (id)\n  read opts-\u003enetns_id (id)\n  put_net(net) /* no matching get */\n\nThe reverse transition leaks the reference.  Repeating the unmatched put\ncan destroy a live namespace and crash later users.\n\nThe kernel reported:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef]\n  RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700\n  Call Trace:\n   __sys_bpf+0x1662/0x50c0\n   __x64_sys_bpf+0x73/0xb0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n  Kernel panic - not syncing: Fatal exception\n\nSnapshot every input field of opts with READ_ONCE() before validating or\nusing it.  The netns_id snapshot keeps the namespace get/put pair\nbalanced, while the other snapshots keep the remaining options from\nchanging partway through an invocation.  The individual reads can still\nobserve an inconsistent combination during a concurrent update, but each\nselected field value remains stable for that invocation.","status":"published","published":"2026-08-22T16:16:46Z","modified":"2026-11-07T14:20:34.91007966Z","updated_at":"2026-11-07T14:48:11.583685Z"},{"id":"openSUSE-SU-2026:22167-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-2026-31731: thermal: core: Address thermal zone removal races with resume (bsc#1264042).\n- CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests (bsc#1267430).\n- CVE-2026-53108: powerpc/64s: Fix unmap race with PMD migration entries (bsc#1269561).\n- CVE-2026-63830: net: skmsg: preserve sg.copy across SG transforms (bsc#1272178).\n- CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1273764).\n- CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback (bsc#1272898).\n- CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling (bsc#1272901).\n- CVE-2026-64062: netfs: Fix potential deadlock in write-through mode (bsc#1272952).\n- CVE-2026-64063: netfs: Fix streaming write being overwritten (bsc#1272955).\n- CVE-2026-64064: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (bsc#1272956).\n- CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs (bsc#1272509).\n- CVE-2026-64116: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (bsc#1273751).\n- CVE-2026-64280: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() (bsc#1273599).\n- CVE-2026-64424: netpoll: fix a use-after-free on shutdown path (bsc#1274256).\n- CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path (bsc#1274039).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64461: PCI: mediatek: Fix IRQ domain leak when port fails to enable (bsc#1273865).\n- CVE-2026-68233: drm/vc4: Shut down BO cache timer before teardown (bsc#1275644).\n- CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop (bsc#1275785).\n- CVE-2026-68242: drm/i915/gt: Fix NULL deref on sched_engine alloc failure (bsc#1275786).\n- CVE-2026-68323: tipc: serialize udp bearer replicast list updates (bsc#1274653).\n- CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list (bsc#1276791).\n- CVE-2026-72040: ipmi: fix refcount leak in i_ipmi_request() (bsc#1276836).\n- CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send (bsc#1275510).\n- CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB (bsc#1277174).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72172: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE (bsc#1277691).\n- CVE-2026-72174: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() (bsc#1277695).\n- CVE-2026-72212: mm/memory_hotplug: fix incorrect altmap passing in error path (bsc#1277602).\n- CVE-2026-72213: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch (bsc#1277603).\n- CVE-2026-72236: s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (bsc#1277614).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72305: VDUSE: avoid leaking information to userspace (bsc#1277747).\n- CVE-2026-72319: ipvs: fix PMTU for GUE/GRE tunnel ICMP errors (bsc#1275964).\n- CVE-2026-72355: netfs: Fix barriering when walking subrequest list (bsc#1276330).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72493: net: serialize netif_running() check in enqueue_to_backlog() (bsc#1276951).\n- CVE-2026-74306: vfio/qat: fix f_pos race in qat_vf_resume_write() (bsc#1276907).\n- CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths (bsc#1276873).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal (bsc#1278232).\n- CVE-2026-74544: net/sched: cls_u32: validate offshift to prevent shift-out-of-bounds (bsc#1277894).\n- CVE-2026-74578: crypto: algif_skcipher - force synchronous processing (bsc#1275564).\n- CVE-2026-74583: net/sched: cls_route: fix fastmap use-after-free on filter (bsc#1277889).\n- CVE-2026-74587: sctp: fix use-after-free of cached ASCONF chunk (bsc#1277821).\n- CVE-2026-74611: tls: rx: restore msg_iter before TLS 1.3 optimistic retry (bsc#1277804).\n- CVE-2026-74614: vsock/virtio: read virtqueues under worker locks (bsc#1277931).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: bpf: Fix netns reference imbalance in conntrack kfuncs (bsc#1277890).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80893: mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork() (bsc#1279706).\n- CVE-2026-80977: net: skbuff: don't touch shared zerocopy state in skb_tx_error() (bsc#1280259).\n- CVE-2026-89528: svcrdma: Reject Read lists that exceed the page budget (bsc#1280743).\n- CVE-2026-89558: md/raid10: fix still_degraded being inverted in raid10_sync_request() (bsc#1280552).\n- CVE-2026-89593: hugetlb: only adjust reservation during unmapping if mapcount is 0 (bsc#1280229).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89754: mm/pagewalk: fix stale walk-\u003eaction escaping walk_pmd_range() (bsc#1280769).\n- CVE-2026-89755: mm/migrate_device: clear stale mapping after freeing swapcache (bsc#1280770).\n- CVE-2026-89778: isofs: fix out-of-bounds page array access on empty zisofs block (bsc#1280966).\n- CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (bsc#1281144).\n- CVE-2026-89987: mm/huge_memory: transfer the pmd dirty bit to the folio on zap (bsc#1281819).\n- CVE-2026-90011: scsi: target: iscsi: Reserve a terminator byte for the login payload (bsc#1281280).\n- CVE-2026-90283: hugetlbfs: release subpool on fill_super failure (bsc#1281771).\n- CVE-2026-90289: drm/amd/display: Resize MST HDCP per-connector arrays to 32 (bsc#1281726).\n- CVE-2026-93066: x86/mm/pat: Take cpa_lock around large-page collapse (bsc#1282274).\n- CVE-2026-93134: printk: Fix possible console use-after-free (bsc#1281162).\n- CVE-2026-93222: signal: avoid shared siginfo namespace rewrites (bsc#1282742).\n- CVE-2026-93252: ocfs2: fix circular locking dependency in ocfs2_init_acl() (bsc#1282784).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access (bsc#1283037).\n- CVE-2026-97415: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (bsc#1282768).\n- CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() (bsc#1282770).\n- CVE-2026-97491: net/rds: Don't sleep inside rds_ib_conn_path_shutdown (bsc#1283142).\n- CVE-2026-97533: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (bsc#1283454).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97555: smb: client: fix heap overflow in DACL owner/group rewrite (bsc#1283851).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97564: smb: client: reject userspace cifs.idmap descriptions (bsc#1283946).\n- CVE-2026-97942: x86/alternatives: Exclude text poking against change_page_attr() (bsc#1283153).\n- CVE-2026-97943: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (bsc#1283158).\n- CVE-2026-97945: x86/mm: Fix user-space data loss with MADV_FREE and THP (bsc#1283144).\n- CVE-2026-98010: net/sched: drr: clamp quantum in change class (bsc#1283823).\n- CVE-2026-98015: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (bsc#1283963).\n- CVE-2026-98016: net/mlx5e: Fix use-after-free race in sample_restore_put() (bsc#1283894).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98077: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() (bsc#1283979).\n- CVE-2026-98089: bonding: alb: fix uninitialized transport header access in alb_determine_nd() (bsc#1283936).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98130: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (bsc#1283835).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98171: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (bsc#1284419).\n- CVE-2026-98173: smb: client: fix use-after-free of iface in cifs_try_adding_channels() (bsc#1284415).\n- CVE-2026-98174: smb: client: fix rlist race and missing initialization (bsc#1284412).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98216: IB/hfi1: Fix the PIO_CRED credit-return mmap (bsc#1284559).\n- CVE-2026-98252: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() (bsc#1284581).\n- CVE-2026-98253: RDMA/ucma: Serialize join and leave on copy_to_user failure (bsc#1284790).\n- CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread() (bsc#1284408).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98269: btrfs: abort transaction on failure to update inode for hole punching and reflinking (bsc#1284606).\n- CVE-2026-98273: x86/kprobes: Fix crash when probing CS CALL instructions (bsc#1284462).\n- CVE-2026-98323: RDMA/siw: Bound fragmented header copies by the remaining length (bsc#1284713).\n- CVE-2026-98347: IB/IPoIB: Avoid restoring OPER_UP after multicast flush (bsc#1284295).\n- CVE-2026-98352: kABI fix for RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted (bsc#1284647).\n- CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails (bsc#1284291).\n- CVE-2026-98357: IB/isert: wait for deferred control PDU completions before releasing the connection (bsc#1284791).\n- CVE-2026-98358: IB/iser: reject a remote invalidation of an unregistered direction (bsc#1284289).\n- CVE-2026-98359: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed (bsc#1284746).\n- CVE-2026-98360: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds (bsc#1284649).\n- CVE-2026-98365: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access (bsc#1284288).\n- CVE-2026-98366: RDMA/rxe: validate access flags before swapping the MR's PD (bsc#1284655).\n- CVE-2026-98367: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept (bsc#1284424).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-99999: ipv4: validate checksum_start before completing checksum (bsc#1285684).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems (git-fixes).\n- arm64: cpufeature: Make PMUVer and PerfMon unsigned (git-fixes).\n- arm64: errata: Add Cortex-A725 erratum 3821522 workaround (git-fixes) Enable workaround by default for aarch64.\n- arm64: errata: Factor out broken AMU const counter cap (git-fixes) Enable this workaround by default for aarch64.\n- arm64: errata: Workaround for SI L1 downstream coherency issue (git-fixes) Enable workaround by default for aarch64.\n- arm64: irq: exclude the softirq stack switch from KCOV (git-fixes).\n- ASoC: adau1372: allow sleepy powerdown GPIOs (git-fixes).\n- ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: cs42l52: Fix the NG Type Switch bit (git-fixes).\n- ASoC: cs42l56: Put the Limiter Cushion control on the limiter register (git-fixes).\n- ASoC: Intel: avs: Reset the stream unless it is already prepared (git-fixes).\n- ASoC: max98371: Fix the Speaker DHT Min Volume bits (git-fixes).\n- ASoC: nau8822: Fix the 128x oversampling switch bits (git-fixes).\n- ASoC: pcm3168a: Fix the DAC zero flag polarity bit (git-fixes).\n- ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM (git-fixes).\n- ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data (stable-fixes).\n- ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality (stable-fixes).\n- ASoC: stm32: spdifrx: fix synchronization state check (git-fixes).\n- ASoC: wm8978: Fix the 128x oversampling switch bits (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btintel_pcie: Add shared HW reset for clean start (git-fixes).\n- Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() (git-fixes).\n- Bluetooth: btintel_pcie: fix TX descriptor bounds check (git-fixes).\n- Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() (git-fixes).\n- Bluetooth: btintel_pcie: use managed IRQ teardown (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Serialize ACL scheduling with channel deletion (git-fixes).\n- Bluetooth: hci_core: Serialize fragmented ISO packet queueing (git-fixes).\n- Bluetooth: hci_sock: Serialize dead-device detachment (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: ISO: Reject concurrent BIS listener setup (git-fixes).\n- Bluetooth: ISO: Serialize concurrent connect calls (git-fixes).\n- Bluetooth: MGMT: Fix status of pending commands flushed on power off (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown (git-fixes).\n- Bluetooth: RFCOMM: free the skb when the DLC has no owner (git-fixes).\n- Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() (git-fixes).\n- crypto: ccp - Add support for PCI device 0x17D8 (jsc#PED-13872).\n- Drivers: hv: Avoid infinite retry loop in init_vp_index() (git-fixes).\n- Drivers: hv: Don't reset VMBus connection state on error/exit paths (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- Drivers: hv: vmbus: fix typo \"substract\" in comment (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set (git-fixes).\n- drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks (git-fixes).\n- drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr (git-fixes).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdkfd: align SDMA doorbell base for shader doorbell writes (git-fixes).\n- drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info (git-fixes).\n- drm/aspeed: Balance the display clock enable on teardown (git-fixes).\n- drm/dp: don't mark the AUX backlight enabled when enabling failed (git-fixes).\n- drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN (git-fixes).\n- drm/gud: don't keep a connector without a CRTC as connector_state (git-fixes).\n- drm/i915/gem: Prevent overstepping exec array boundary (git-fixes).\n- drm/i915/gt: Unmask interrupts only when ACTIVE is true (git-fixes).\n- drm/imagination: Fix reference and vm_bo handling in remap() (git-fixes).\n- drm/imagination: Size page table preallocation by device address (git-fixes).\n- drm/vc4: drain the hangcheck timer and works on V3D unbind (git-fixes).\n- drm/vc4: Fix binner slot allocation failing on an idle GPU (git-fixes).\n- drm/vc4: Free the BO cache size list on teardown (git-fixes).\n- drm/vc4: hdmi: Move packet RAM enable to PM runtime (git-fixes).\n- drm/vc4: Make v3d paths unavailable on any generation newer than vc4 (stable-fixes).\n- gpio: exar: initialize the ID before registering its cleanup (git-fixes).\n- gpio: xilinx: fix runtime PM leak on request error path (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- IB/hfi1: Resolve the credit-return buffer through the send context's node (git-fixes).\n- iio: accel: kionix-kx022a: Prevent memory leak and fix state (git-fixes).\n- iio: accel: kx022a: Use cleanup.h helpers (stable-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: bu27034: simplify using guard(mutex) (stable-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: rohm-bu27034: Fix error return (git-fixes).\n- iio: light: rohm-bu27034: Fix infinite delay on error (git-fixes).\n- Input: ati_remote2 - fix type confusion in device attribute handlers (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() (git-fixes).\n- KVM: PPC: Book3S HV: Add H_VIRT mapping for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add missing mappings for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users (bsc#1215199).\n- KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls (bsc#1215199).\n- KVM: PPC: Book3S HV: Free the queue pages in error path (bsc#1215199).\n- KVM: PPC: Fix callback check in kvmppc_gsm_refresh_info (jsc#PED-11016 git-fixes).\n- KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form (bsc#1215199).\n- memstick: core: wait for request completion before freeing card (git-fixes).\n- memstick: rtsx_usb_ms: complete requests after eject instead of dropping them (git-fixes).\n- mmc: cavium-octeon: destroy slot platform devices on remove (git-fixes).\n- mmc: cavium-thunderx: destroy slot platform devices on remove (git-fixes).\n- mmc: mtk-sd: Cancel request timeout work on remove (git-fixes).\n- mmc: sdhci-sprd: disable runtime PM on remove (git-fixes).\n- net: mana: reserve RX buffer headroom to fix forwarding performance (git-fixes).\n- net: usb: ax88179_178a: fix rx frame length for non-last packets (git-fixes).\n- net: usb: qmi_wwan: add Quectel EG120K-EA (stable-fixes).\n- PCI: hv: Probe vPCI buses asynchronously (git-fixes).\n- PCI: hv: Warn when wait_for_response() waits indefinitely (git-fixes).\n- pinctrl: amd: Clear S4 wake bits when firmware has _AEI (git-fixes).\n- pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 (git-fixes).\n- pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 (git-fixes).\n- power: supply: ds2780: Fix ds2780_get_capacity() returning raw value (git-fixes).\n- power: supply: Fix maintenance charge table kernel-doc (git-fixes).\n- power: supply: generic-adc-battery: Fix temperature IIO channel conversion (git-fixes).\n- powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved (bsc#1268315 ltc#217645).\n- powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard (bsc#1215199).\n- printk: Handle pre-enabled consoles in the top-level register_console() (bsc#1285989).\n- pseries/plpks: clear SED key data after use (bsc#1215199).\n- pseries/plpks: clear sensitive PLPKS buffers (bsc#1215199).\n- pseries/plpks: clear signed update authentication buffer (bsc#1215199).\n- pseries/plpks: fix error handling in plpks_read_var() (bsc#1215199).\n- pseries/plpks: make narrowing conversions explicit (bsc#1215199).\n- pseries/plpks: validate input to plpks_signed_update_var() (bsc#1215199).\n- regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (git-fixes).\n- regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 (git-fixes).\n- sched/debug: Change SCHED_WARN_ON() to WARN_ON_ONCE() (jsc#PED-14958 bsc#1234634 (Scheduler functional and performance\n  backports SL-16.1) bsc#1282005).\n- sched/eevdf: Update se-\u003evprot in reweight_entity() (bsc#1234634 (Scheduler functional and performance backports\n  SL-16.1) bsc#1282005).\n- sched/fair: Revert 6d71a9c61604 (\"sched/fair: Fix EEVDF entity placement bug causing scheduling lag\") (bsc#1234634\n  (Scheduler functional and performance backports SL-16.1) bsc#1282005).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- tools/hv: fix typo \"retrive\" in comment (git-fixes).\n- tools: gpio: fix building from the top level with O= (git-fixes).\n- tpm: Initialize name_size_alg for non-NULL name in tpm_buf_append_name() (stable-fixes).\n- usb: f81604: fix struct f81604_int_data size mismatch (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- wifi: ath9k: reject short WMI command responses (git-fixes).\n- wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: atk9k: Revert \"wifi: ath9k: reject short WMI command responses\" (stable-fixes).\n- wifi: brcmfmac: fix P2P device removal race in brcmf_detach() (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: keep fallback association elements alive (git-fixes).\n- wifi: mac80211: keep paired old chanctx alive (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: reject invalid 320 MHz CSA bandwidth (git-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mt76: mt792x: pick the SAR table layout from the table itself (git-fixes).\n- wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit (git-fixes).\n- wifi: mt76: mt7915: disable rx napi when removing device (git-fixes).\n- wifi: mt76: mt7925: don't put the band auto marker in TGID (git-fixes).\n- wifi: mt76: mt7925: restore the legacy BSS after MLO teardown (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wifi: wlcore: Fix runtime PM leak in wlcore_remove() (git-fixes).\n- x86/bugs: Adapt SRSO mitigation to Zen6 (bsc#1282615).\n- x86/bugs: Add attack vector controls for VMSCAPE (git-fixes).\n- x86/bugs: Remove dead code which might prevent from building (git-fixes).\n- x86/bugs: Remove uses of cpu_mitigations_off() (git-fixes).\n- x86/bugs: Remove X86_BUG_MMIO_UNKNOWN (git-fixes).\n- x86/bugs: Simplify SSB cmdline parsing (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2 (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2_user (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/mm: Drop unnecessary PMD page copy when freeing (git-fixes).\n","status":"published","published":"2026-10-24T12:35:03Z","modified":"2026-10-25T17:30:03.891806908Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:24386-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-2026-31731: thermal: core: Address thermal zone removal races with resume (bsc#1264042).\n- CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests (bsc#1267430).\n- CVE-2026-53108: powerpc/64s: Fix unmap race with PMD migration entries (bsc#1269561).\n- CVE-2026-63830: net: skmsg: preserve sg.copy across SG transforms (bsc#1272178).\n- CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1273764).\n- CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback (bsc#1272898).\n- CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling (bsc#1272901).\n- CVE-2026-64062: netfs: Fix potential deadlock in write-through mode (bsc#1272952).\n- CVE-2026-64063: netfs: Fix streaming write being overwritten (bsc#1272955).\n- CVE-2026-64064: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (bsc#1272956).\n- CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs (bsc#1272509).\n- CVE-2026-64116: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (bsc#1273751).\n- CVE-2026-64280: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() (bsc#1273599).\n- CVE-2026-64424: netpoll: fix a use-after-free on shutdown path (bsc#1274256).\n- CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path (bsc#1274039).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64461: PCI: mediatek: Fix IRQ domain leak when port fails to enable (bsc#1273865).\n- CVE-2026-68233: drm/vc4: Shut down BO cache timer before teardown (bsc#1275644).\n- CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop (bsc#1275785).\n- CVE-2026-68242: drm/i915/gt: Fix NULL deref on sched_engine alloc failure (bsc#1275786).\n- CVE-2026-68323: tipc: serialize udp bearer replicast list updates (bsc#1274653).\n- CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list (bsc#1276791).\n- CVE-2026-72040: ipmi: fix refcount leak in i_ipmi_request() (bsc#1276836).\n- CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send (bsc#1275510).\n- CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB (bsc#1277174).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72172: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE (bsc#1277691).\n- CVE-2026-72174: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() (bsc#1277695).\n- CVE-2026-72212: mm/memory_hotplug: fix incorrect altmap passing in error path (bsc#1277602).\n- CVE-2026-72213: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch (bsc#1277603).\n- CVE-2026-72236: s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (bsc#1277614).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72305: VDUSE: avoid leaking information to userspace (bsc#1277747).\n- CVE-2026-72319: ipvs: fix PMTU for GUE/GRE tunnel ICMP errors (bsc#1275964).\n- CVE-2026-72355: netfs: Fix barriering when walking subrequest list (bsc#1276330).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72493: net: serialize netif_running() check in enqueue_to_backlog() (bsc#1276951).\n- CVE-2026-74306: vfio/qat: fix f_pos race in qat_vf_resume_write() (bsc#1276907).\n- CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths (bsc#1276873).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal (bsc#1278232).\n- CVE-2026-74544: net/sched: cls_u32: validate offshift to prevent shift-out-of-bounds (bsc#1277894).\n- CVE-2026-74578: crypto: algif_skcipher - force synchronous processing (bsc#1275564).\n- CVE-2026-74583: net/sched: cls_route: fix fastmap use-after-free on filter (bsc#1277889).\n- CVE-2026-74587: sctp: fix use-after-free of cached ASCONF chunk (bsc#1277821).\n- CVE-2026-74611: tls: rx: restore msg_iter before TLS 1.3 optimistic retry (bsc#1277804).\n- CVE-2026-74614: vsock/virtio: read virtqueues under worker locks (bsc#1277931).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: bpf: Fix netns reference imbalance in conntrack kfuncs (bsc#1277890).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80893: mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork() (bsc#1279706).\n- CVE-2026-80977: net: skbuff: don't touch shared zerocopy state in skb_tx_error() (bsc#1280259).\n- CVE-2026-89528: svcrdma: Reject Read lists that exceed the page budget (bsc#1280743).\n- CVE-2026-89558: md/raid10: fix still_degraded being inverted in raid10_sync_request() (bsc#1280552).\n- CVE-2026-89593: hugetlb: only adjust reservation during unmapping if mapcount is 0 (bsc#1280229).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89754: mm/pagewalk: fix stale walk-\u003eaction escaping walk_pmd_range() (bsc#1280769).\n- CVE-2026-89755: mm/migrate_device: clear stale mapping after freeing swapcache (bsc#1280770).\n- CVE-2026-89778: isofs: fix out-of-bounds page array access on empty zisofs block (bsc#1280966).\n- CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (bsc#1281144).\n- CVE-2026-89987: mm/huge_memory: transfer the pmd dirty bit to the folio on zap (bsc#1281819).\n- CVE-2026-90011: scsi: target: iscsi: Reserve a terminator byte for the login payload (bsc#1281280).\n- CVE-2026-90283: hugetlbfs: release subpool on fill_super failure (bsc#1281771).\n- CVE-2026-90289: drm/amd/display: Resize MST HDCP per-connector arrays to 32 (bsc#1281726).\n- CVE-2026-93066: x86/mm/pat: Take cpa_lock around large-page collapse (bsc#1282274).\n- CVE-2026-93134: printk: Fix possible console use-after-free (bsc#1281162).\n- CVE-2026-93222: signal: avoid shared siginfo namespace rewrites (bsc#1282742).\n- CVE-2026-93252: ocfs2: fix circular locking dependency in ocfs2_init_acl() (bsc#1282784).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access (bsc#1283037).\n- CVE-2026-97415: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (bsc#1282768).\n- CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() (bsc#1282770).\n- CVE-2026-97491: net/rds: Don't sleep inside rds_ib_conn_path_shutdown (bsc#1283142).\n- CVE-2026-97533: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (bsc#1283454).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97555: smb: client: fix heap overflow in DACL owner/group rewrite (bsc#1283851).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97564: smb: client: reject userspace cifs.idmap descriptions (bsc#1283946).\n- CVE-2026-97942: x86/alternatives: Exclude text poking against change_page_attr() (bsc#1283153).\n- CVE-2026-97943: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (bsc#1283158).\n- CVE-2026-97945: x86/mm: Fix user-space data loss with MADV_FREE and THP (bsc#1283144).\n- CVE-2026-98010: net/sched: drr: clamp quantum in change class (bsc#1283823).\n- CVE-2026-98015: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (bsc#1283963).\n- CVE-2026-98016: net/mlx5e: Fix use-after-free race in sample_restore_put() (bsc#1283894).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98077: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() (bsc#1283979).\n- CVE-2026-98089: bonding: alb: fix uninitialized transport header access in alb_determine_nd() (bsc#1283936).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98130: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (bsc#1283835).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98171: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (bsc#1284419).\n- CVE-2026-98173: smb: client: fix use-after-free of iface in cifs_try_adding_channels() (bsc#1284415).\n- CVE-2026-98174: smb: client: fix rlist race and missing initialization (bsc#1284412).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98216: IB/hfi1: Fix the PIO_CRED credit-return mmap (bsc#1284559).\n- CVE-2026-98252: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() (bsc#1284581).\n- CVE-2026-98253: RDMA/ucma: Serialize join and leave on copy_to_user failure (bsc#1284790).\n- CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread() (bsc#1284408).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98269: btrfs: abort transaction on failure to update inode for hole punching and reflinking (bsc#1284606).\n- CVE-2026-98273: x86/kprobes: Fix crash when probing CS CALL instructions (bsc#1284462).\n- CVE-2026-98323: RDMA/siw: Bound fragmented header copies by the remaining length (bsc#1284713).\n- CVE-2026-98347: IB/IPoIB: Avoid restoring OPER_UP after multicast flush (bsc#1284295).\n- CVE-2026-98352: kABI fix for RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted (bsc#1284647).\n- CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails (bsc#1284291).\n- CVE-2026-98357: IB/isert: wait for deferred control PDU completions before releasing the connection (bsc#1284791).\n- CVE-2026-98358: IB/iser: reject a remote invalidation of an unregistered direction (bsc#1284289).\n- CVE-2026-98359: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed (bsc#1284746).\n- CVE-2026-98360: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds (bsc#1284649).\n- CVE-2026-98365: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access (bsc#1284288).\n- CVE-2026-98366: RDMA/rxe: validate access flags before swapping the MR's PD (bsc#1284655).\n- CVE-2026-98367: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept (bsc#1284424).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-99999: ipv4: validate checksum_start before completing checksum (bsc#1285684).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems (git-fixes).\n- arm64: cpufeature: Make PMUVer and PerfMon unsigned (git-fixes).\n- arm64: errata: Add Cortex-A725 erratum 3821522 workaround (git-fixes) Enable workaround by default for aarch64.\n- arm64: errata: Factor out broken AMU const counter cap (git-fixes) Enable this workaround by default for aarch64.\n- arm64: errata: Workaround for SI L1 downstream coherency issue (git-fixes) Enable workaround by default for aarch64.\n- arm64: irq: exclude the softirq stack switch from KCOV (git-fixes).\n- ASoC: adau1372: allow sleepy powerdown GPIOs (git-fixes).\n- ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: cs42l52: Fix the NG Type Switch bit (git-fixes).\n- ASoC: cs42l56: Put the Limiter Cushion control on the limiter register (git-fixes).\n- ASoC: Intel: avs: Reset the stream unless it is already prepared (git-fixes).\n- ASoC: max98371: Fix the Speaker DHT Min Volume bits (git-fixes).\n- ASoC: nau8822: Fix the 128x oversampling switch bits (git-fixes).\n- ASoC: pcm3168a: Fix the DAC zero flag polarity bit (git-fixes).\n- ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM (git-fixes).\n- ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data (stable-fixes).\n- ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality (stable-fixes).\n- ASoC: stm32: spdifrx: fix synchronization state check (git-fixes).\n- ASoC: wm8978: Fix the 128x oversampling switch bits (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btintel_pcie: Add shared HW reset for clean start (git-fixes).\n- Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() (git-fixes).\n- Bluetooth: btintel_pcie: fix TX descriptor bounds check (git-fixes).\n- Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() (git-fixes).\n- Bluetooth: btintel_pcie: use managed IRQ teardown (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Serialize ACL scheduling with channel deletion (git-fixes).\n- Bluetooth: hci_core: Serialize fragmented ISO packet queueing (git-fixes).\n- Bluetooth: hci_sock: Serialize dead-device detachment (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: ISO: Reject concurrent BIS listener setup (git-fixes).\n- Bluetooth: ISO: Serialize concurrent connect calls (git-fixes).\n- Bluetooth: MGMT: Fix status of pending commands flushed on power off (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown (git-fixes).\n- Bluetooth: RFCOMM: free the skb when the DLC has no owner (git-fixes).\n- Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() (git-fixes).\n- crypto: ccp - Add support for PCI device 0x17D8 (jsc#PED-13872).\n- Drivers: hv: Avoid infinite retry loop in init_vp_index() (git-fixes).\n- Drivers: hv: Don't reset VMBus connection state on error/exit paths (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- Drivers: hv: vmbus: fix typo \"substract\" in comment (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set (git-fixes).\n- drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks (git-fixes).\n- drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr (git-fixes).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdkfd: align SDMA doorbell base for shader doorbell writes (git-fixes).\n- drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info (git-fixes).\n- drm/aspeed: Balance the display clock enable on teardown (git-fixes).\n- drm/dp: don't mark the AUX backlight enabled when enabling failed (git-fixes).\n- drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN (git-fixes).\n- drm/gud: don't keep a connector without a CRTC as connector_state (git-fixes).\n- drm/i915/gem: Prevent overstepping exec array boundary (git-fixes).\n- drm/i915/gt: Unmask interrupts only when ACTIVE is true (git-fixes).\n- drm/imagination: Fix reference and vm_bo handling in remap() (git-fixes).\n- drm/imagination: Size page table preallocation by device address (git-fixes).\n- drm/vc4: drain the hangcheck timer and works on V3D unbind (git-fixes).\n- drm/vc4: Fix binner slot allocation failing on an idle GPU (git-fixes).\n- drm/vc4: Free the BO cache size list on teardown (git-fixes).\n- drm/vc4: hdmi: Move packet RAM enable to PM runtime (git-fixes).\n- drm/vc4: Make v3d paths unavailable on any generation newer than vc4 (stable-fixes).\n- gpio: exar: initialize the ID before registering its cleanup (git-fixes).\n- gpio: xilinx: fix runtime PM leak on request error path (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- IB/hfi1: Resolve the credit-return buffer through the send context's node (git-fixes).\n- iio: accel: kionix-kx022a: Prevent memory leak and fix state (git-fixes).\n- iio: accel: kx022a: Use cleanup.h helpers (stable-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: bu27034: simplify using guard(mutex) (stable-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: rohm-bu27034: Fix error return (git-fixes).\n- iio: light: rohm-bu27034: Fix infinite delay on error (git-fixes).\n- Input: ati_remote2 - fix type confusion in device attribute handlers (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() (git-fixes).\n- KVM: PPC: Book3S HV: Add H_VIRT mapping for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add missing mappings for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users (bsc#1215199).\n- KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls (bsc#1215199).\n- KVM: PPC: Book3S HV: Free the queue pages in error path (bsc#1215199).\n- KVM: PPC: Fix callback check in kvmppc_gsm_refresh_info (jsc#PED-11016 git-fixes).\n- KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form (bsc#1215199).\n- memstick: core: wait for request completion before freeing card (git-fixes).\n- memstick: rtsx_usb_ms: complete requests after eject instead of dropping them (git-fixes).\n- mmc: cavium-octeon: destroy slot platform devices on remove (git-fixes).\n- mmc: cavium-thunderx: destroy slot platform devices on remove (git-fixes).\n- mmc: mtk-sd: Cancel request timeout work on remove (git-fixes).\n- mmc: sdhci-sprd: disable runtime PM on remove (git-fixes).\n- net: mana: reserve RX buffer headroom to fix forwarding performance (git-fixes).\n- net: usb: ax88179_178a: fix rx frame length for non-last packets (git-fixes).\n- net: usb: qmi_wwan: add Quectel EG120K-EA (stable-fixes).\n- PCI: hv: Probe vPCI buses asynchronously (git-fixes).\n- PCI: hv: Warn when wait_for_response() waits indefinitely (git-fixes).\n- pinctrl: amd: Clear S4 wake bits when firmware has _AEI (git-fixes).\n- pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 (git-fixes).\n- pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 (git-fixes).\n- power: supply: ds2780: Fix ds2780_get_capacity() returning raw value (git-fixes).\n- power: supply: Fix maintenance charge table kernel-doc (git-fixes).\n- power: supply: generic-adc-battery: Fix temperature IIO channel conversion (git-fixes).\n- powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved (bsc#1268315 ltc#217645).\n- powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard (bsc#1215199).\n- printk: Handle pre-enabled consoles in the top-level register_console() (bsc#1285989).\n- pseries/plpks: clear SED key data after use (bsc#1215199).\n- pseries/plpks: clear sensitive PLPKS buffers (bsc#1215199).\n- pseries/plpks: clear signed update authentication buffer (bsc#1215199).\n- pseries/plpks: fix error handling in plpks_read_var() (bsc#1215199).\n- pseries/plpks: make narrowing conversions explicit (bsc#1215199).\n- pseries/plpks: validate input to plpks_signed_update_var() (bsc#1215199).\n- regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (git-fixes).\n- regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 (git-fixes).\n- sched/debug: Change SCHED_WARN_ON() to WARN_ON_ONCE() (jsc#PED-14958 bsc#1234634 (Scheduler functional and performance\n  backports SL-16.1) bsc#1282005).\n- sched/eevdf: Update se-\u003evprot in reweight_entity() (bsc#1234634 (Scheduler functional and performance backports\n  SL-16.1) bsc#1282005).\n- sched/fair: Revert 6d71a9c61604 (\"sched/fair: Fix EEVDF entity placement bug causing scheduling lag\") (bsc#1234634\n  (Scheduler functional and performance backports SL-16.1) bsc#1282005).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- tools/hv: fix typo \"retrive\" in comment (git-fixes).\n- tools: gpio: fix building from the top level with O= (git-fixes).\n- tpm: Initialize name_size_alg for non-NULL name in tpm_buf_append_name() (stable-fixes).\n- usb: f81604: fix struct f81604_int_data size mismatch (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- wifi: ath9k: reject short WMI command responses (git-fixes).\n- wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: atk9k: Revert \"wifi: ath9k: reject short WMI command responses\" (stable-fixes).\n- wifi: brcmfmac: fix P2P device removal race in brcmf_detach() (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: keep fallback association elements alive (git-fixes).\n- wifi: mac80211: keep paired old chanctx alive (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: reject invalid 320 MHz CSA bandwidth (git-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mt76: mt792x: pick the SAR table layout from the table itself (git-fixes).\n- wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit (git-fixes).\n- wifi: mt76: mt7915: disable rx napi when removing device (git-fixes).\n- wifi: mt76: mt7925: don't put the band auto marker in TGID (git-fixes).\n- wifi: mt76: mt7925: restore the legacy BSS after MLO teardown (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wifi: wlcore: Fix runtime PM leak in wlcore_remove() (git-fixes).\n- x86/bugs: Adapt SRSO mitigation to Zen6 (bsc#1282615).\n- x86/bugs: Add attack vector controls for VMSCAPE (git-fixes).\n- x86/bugs: Remove dead code which might prevent from building (git-fixes).\n- x86/bugs: Remove uses of cpu_mitigations_off() (git-fixes).\n- x86/bugs: Remove X86_BUG_MMIO_UNKNOWN (git-fixes).\n- x86/bugs: Simplify SSB cmdline parsing (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2 (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2_user (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/mm: Drop unnecessary PMD page copy when freeing (git-fixes).\n","status":"published","published":"2026-10-24T10:42:33Z","modified":"2026-10-30T17:23:14.987197283Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24422-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-2026-31731: thermal: core: Address thermal zone removal races with resume (bsc#1264042).\n- CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests (bsc#1267430).\n- CVE-2026-53108: powerpc/64s: Fix unmap race with PMD migration entries (bsc#1269561).\n- CVE-2026-63830: net: skmsg: preserve sg.copy across SG transforms (bsc#1272178).\n- CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1273764).\n- CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback (bsc#1272898).\n- CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling (bsc#1272901).\n- CVE-2026-64062: netfs: Fix potential deadlock in write-through mode (bsc#1272952).\n- CVE-2026-64063: netfs: Fix streaming write being overwritten (bsc#1272955).\n- CVE-2026-64064: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (bsc#1272956).\n- CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs (bsc#1272509).\n- CVE-2026-64116: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (bsc#1273751).\n- CVE-2026-64280: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() (bsc#1273599).\n- CVE-2026-64424: netpoll: fix a use-after-free on shutdown path (bsc#1274256).\n- CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path (bsc#1274039).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64461: PCI: mediatek: Fix IRQ domain leak when port fails to enable (bsc#1273865).\n- CVE-2026-68233: drm/vc4: Shut down BO cache timer before teardown (bsc#1275644).\n- CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop (bsc#1275785).\n- CVE-2026-68242: drm/i915/gt: Fix NULL deref on sched_engine alloc failure (bsc#1275786).\n- CVE-2026-68323: tipc: serialize udp bearer replicast list updates (bsc#1274653).\n- CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list (bsc#1276791).\n- CVE-2026-72040: ipmi: fix refcount leak in i_ipmi_request() (bsc#1276836).\n- CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send (bsc#1275510).\n- CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB (bsc#1277174).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72172: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE (bsc#1277691).\n- CVE-2026-72174: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() (bsc#1277695).\n- CVE-2026-72212: mm/memory_hotplug: fix incorrect altmap passing in error path (bsc#1277602).\n- CVE-2026-72213: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch (bsc#1277603).\n- CVE-2026-72236: s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (bsc#1277614).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72305: VDUSE: avoid leaking information to userspace (bsc#1277747).\n- CVE-2026-72319: ipvs: fix PMTU for GUE/GRE tunnel ICMP errors (bsc#1275964).\n- CVE-2026-72355: netfs: Fix barriering when walking subrequest list (bsc#1276330).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72493: net: serialize netif_running() check in enqueue_to_backlog() (bsc#1276951).\n- CVE-2026-74306: vfio/qat: fix f_pos race in qat_vf_resume_write() (bsc#1276907).\n- CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths (bsc#1276873).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal (bsc#1278232).\n- CVE-2026-74544: net/sched: cls_u32: validate offshift to prevent shift-out-of-bounds (bsc#1277894).\n- CVE-2026-74578: crypto: algif_skcipher - force synchronous processing (bsc#1275564).\n- CVE-2026-74583: net/sched: cls_route: fix fastmap use-after-free on filter (bsc#1277889).\n- CVE-2026-74587: sctp: fix use-after-free of cached ASCONF chunk (bsc#1277821).\n- CVE-2026-74611: tls: rx: restore msg_iter before TLS 1.3 optimistic retry (bsc#1277804).\n- CVE-2026-74614: vsock/virtio: read virtqueues under worker locks (bsc#1277931).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: bpf: Fix netns reference imbalance in conntrack kfuncs (bsc#1277890).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80893: mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork() (bsc#1279706).\n- CVE-2026-80977: net: skbuff: don't touch shared zerocopy state in skb_tx_error() (bsc#1280259).\n- CVE-2026-89528: svcrdma: Reject Read lists that exceed the page budget (bsc#1280743).\n- CVE-2026-89558: md/raid10: fix still_degraded being inverted in raid10_sync_request() (bsc#1280552).\n- CVE-2026-89593: hugetlb: only adjust reservation during unmapping if mapcount is 0 (bsc#1280229).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89754: mm/pagewalk: fix stale walk-\u003eaction escaping walk_pmd_range() (bsc#1280769).\n- CVE-2026-89755: mm/migrate_device: clear stale mapping after freeing swapcache (bsc#1280770).\n- CVE-2026-89778: isofs: fix out-of-bounds page array access on empty zisofs block (bsc#1280966).\n- CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (bsc#1281144).\n- CVE-2026-89987: mm/huge_memory: transfer the pmd dirty bit to the folio on zap (bsc#1281819).\n- CVE-2026-90011: scsi: target: iscsi: Reserve a terminator byte for the login payload (bsc#1281280).\n- CVE-2026-90283: hugetlbfs: release subpool on fill_super failure (bsc#1281771).\n- CVE-2026-90289: drm/amd/display: Resize MST HDCP per-connector arrays to 32 (bsc#1281726).\n- CVE-2026-93066: x86/mm/pat: Take cpa_lock around large-page collapse (bsc#1282274).\n- CVE-2026-93134: printk: Fix possible console use-after-free (bsc#1281162).\n- CVE-2026-93222: signal: avoid shared siginfo namespace rewrites (bsc#1282742).\n- CVE-2026-93252: ocfs2: fix circular locking dependency in ocfs2_init_acl() (bsc#1282784).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access (bsc#1283037).\n- CVE-2026-97415: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (bsc#1282768).\n- CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() (bsc#1282770).\n- CVE-2026-97491: net/rds: Don't sleep inside rds_ib_conn_path_shutdown (bsc#1283142).\n- CVE-2026-97533: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (bsc#1283454).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97555: smb: client: fix heap overflow in DACL owner/group rewrite (bsc#1283851).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97564: smb: client: reject userspace cifs.idmap descriptions (bsc#1283946).\n- CVE-2026-97942: x86/alternatives: Exclude text poking against change_page_attr() (bsc#1283153).\n- CVE-2026-97943: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (bsc#1283158).\n- CVE-2026-97945: x86/mm: Fix user-space data loss with MADV_FREE and THP (bsc#1283144).\n- CVE-2026-98010: net/sched: drr: clamp quantum in change class (bsc#1283823).\n- CVE-2026-98015: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (bsc#1283963).\n- CVE-2026-98016: net/mlx5e: Fix use-after-free race in sample_restore_put() (bsc#1283894).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98077: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() (bsc#1283979).\n- CVE-2026-98089: bonding: alb: fix uninitialized transport header access in alb_determine_nd() (bsc#1283936).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98130: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (bsc#1283835).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98171: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (bsc#1284419).\n- CVE-2026-98173: smb: client: fix use-after-free of iface in cifs_try_adding_channels() (bsc#1284415).\n- CVE-2026-98174: smb: client: fix rlist race and missing initialization (bsc#1284412).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98216: IB/hfi1: Fix the PIO_CRED credit-return mmap (bsc#1284559).\n- CVE-2026-98252: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() (bsc#1284581).\n- CVE-2026-98253: RDMA/ucma: Serialize join and leave on copy_to_user failure (bsc#1284790).\n- CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread() (bsc#1284408).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98269: btrfs: abort transaction on failure to update inode for hole punching and reflinking (bsc#1284606).\n- CVE-2026-98273: x86/kprobes: Fix crash when probing CS CALL instructions (bsc#1284462).\n- CVE-2026-98323: RDMA/siw: Bound fragmented header copies by the remaining length (bsc#1284713).\n- CVE-2026-98347: IB/IPoIB: Avoid restoring OPER_UP after multicast flush (bsc#1284295).\n- CVE-2026-98352: kABI fix for RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted (bsc#1284647).\n- CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails (bsc#1284291).\n- CVE-2026-98357: IB/isert: wait for deferred control PDU completions before releasing the connection (bsc#1284791).\n- CVE-2026-98358: IB/iser: reject a remote invalidation of an unregistered direction (bsc#1284289).\n- CVE-2026-98359: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed (bsc#1284746).\n- CVE-2026-98360: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds (bsc#1284649).\n- CVE-2026-98365: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access (bsc#1284288).\n- CVE-2026-98366: RDMA/rxe: validate access flags before swapping the MR's PD (bsc#1284655).\n- CVE-2026-98367: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept (bsc#1284424).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-99999: ipv4: validate checksum_start before completing checksum (bsc#1285684).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems (git-fixes).\n- arm64: cpufeature: Make PMUVer and PerfMon unsigned (git-fixes).\n- arm64: errata: Add Cortex-A725 erratum 3821522 workaround (git-fixes) Enable workaround by default for aarch64.\n- arm64: errata: Factor out broken AMU const counter cap (git-fixes) Enable this workaround by default for aarch64.\n- arm64: errata: Workaround for SI L1 downstream coherency issue (git-fixes) Enable workaround by default for aarch64.\n- arm64: irq: exclude the softirq stack switch from KCOV (git-fixes).\n- ASoC: adau1372: allow sleepy powerdown GPIOs (git-fixes).\n- ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: cs42l52: Fix the NG Type Switch bit (git-fixes).\n- ASoC: cs42l56: Put the Limiter Cushion control on the limiter register (git-fixes).\n- ASoC: Intel: avs: Reset the stream unless it is already prepared (git-fixes).\n- ASoC: max98371: Fix the Speaker DHT Min Volume bits (git-fixes).\n- ASoC: nau8822: Fix the 128x oversampling switch bits (git-fixes).\n- ASoC: pcm3168a: Fix the DAC zero flag polarity bit (git-fixes).\n- ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM (git-fixes).\n- ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data (stable-fixes).\n- ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality (stable-fixes).\n- ASoC: stm32: spdifrx: fix synchronization state check (git-fixes).\n- ASoC: wm8978: Fix the 128x oversampling switch bits (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btintel_pcie: Add shared HW reset for clean start (git-fixes).\n- Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() (git-fixes).\n- Bluetooth: btintel_pcie: fix TX descriptor bounds check (git-fixes).\n- Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() (git-fixes).\n- Bluetooth: btintel_pcie: use managed IRQ teardown (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Serialize ACL scheduling with channel deletion (git-fixes).\n- Bluetooth: hci_core: Serialize fragmented ISO packet queueing (git-fixes).\n- Bluetooth: hci_sock: Serialize dead-device detachment (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: ISO: Reject concurrent BIS listener setup (git-fixes).\n- Bluetooth: ISO: Serialize concurrent connect calls (git-fixes).\n- Bluetooth: MGMT: Fix status of pending commands flushed on power off (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown (git-fixes).\n- Bluetooth: RFCOMM: free the skb when the DLC has no owner (git-fixes).\n- Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() (git-fixes).\n- crypto: ccp - Add support for PCI device 0x17D8 (jsc#PED-13872).\n- Drivers: hv: Avoid infinite retry loop in init_vp_index() (git-fixes).\n- Drivers: hv: Don't reset VMBus connection state on error/exit paths (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- Drivers: hv: vmbus: fix typo \"substract\" in comment (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set (git-fixes).\n- drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks (git-fixes).\n- drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr (git-fixes).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdkfd: align SDMA doorbell base for shader doorbell writes (git-fixes).\n- drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info (git-fixes).\n- drm/aspeed: Balance the display clock enable on teardown (git-fixes).\n- drm/dp: don't mark the AUX backlight enabled when enabling failed (git-fixes).\n- drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN (git-fixes).\n- drm/gud: don't keep a connector without a CRTC as connector_state (git-fixes).\n- drm/i915/gem: Prevent overstepping exec array boundary (git-fixes).\n- drm/i915/gt: Unmask interrupts only when ACTIVE is true (git-fixes).\n- drm/imagination: Fix reference and vm_bo handling in remap() (git-fixes).\n- drm/imagination: Size page table preallocation by device address (git-fixes).\n- drm/vc4: drain the hangcheck timer and works on V3D unbind (git-fixes).\n- drm/vc4: Fix binner slot allocation failing on an idle GPU (git-fixes).\n- drm/vc4: Free the BO cache size list on teardown (git-fixes).\n- drm/vc4: hdmi: Move packet RAM enable to PM runtime (git-fixes).\n- drm/vc4: Make v3d paths unavailable on any generation newer than vc4 (stable-fixes).\n- gpio: exar: initialize the ID before registering its cleanup (git-fixes).\n- gpio: xilinx: fix runtime PM leak on request error path (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- IB/hfi1: Resolve the credit-return buffer through the send context's node (git-fixes).\n- iio: accel: kionix-kx022a: Prevent memory leak and fix state (git-fixes).\n- iio: accel: kx022a: Use cleanup.h helpers (stable-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: bu27034: simplify using guard(mutex) (stable-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: rohm-bu27034: Fix error return (git-fixes).\n- iio: light: rohm-bu27034: Fix infinite delay on error (git-fixes).\n- Input: ati_remote2 - fix type confusion in device attribute handlers (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() (git-fixes).\n- KVM: PPC: Book3S HV: Add H_VIRT mapping for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add missing mappings for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users (bsc#1215199).\n- KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls (bsc#1215199).\n- KVM: PPC: Book3S HV: Free the queue pages in error path (bsc#1215199).\n- KVM: PPC: Fix callback check in kvmppc_gsm_refresh_info (jsc#PED-11016 git-fixes).\n- KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form (bsc#1215199).\n- memstick: core: wait for request completion before freeing card (git-fixes).\n- memstick: rtsx_usb_ms: complete requests after eject instead of dropping them (git-fixes).\n- mmc: cavium-octeon: destroy slot platform devices on remove (git-fixes).\n- mmc: cavium-thunderx: destroy slot platform devices on remove (git-fixes).\n- mmc: mtk-sd: Cancel request timeout work on remove (git-fixes).\n- mmc: sdhci-sprd: disable runtime PM on remove (git-fixes).\n- net: mana: reserve RX buffer headroom to fix forwarding performance (git-fixes).\n- net: usb: ax88179_178a: fix rx frame length for non-last packets (git-fixes).\n- net: usb: qmi_wwan: add Quectel EG120K-EA (stable-fixes).\n- PCI: hv: Probe vPCI buses asynchronously (git-fixes).\n- PCI: hv: Warn when wait_for_response() waits indefinitely (git-fixes).\n- pinctrl: amd: Clear S4 wake bits when firmware has _AEI (git-fixes).\n- pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 (git-fixes).\n- pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 (git-fixes).\n- power: supply: ds2780: Fix ds2780_get_capacity() returning raw value (git-fixes).\n- power: supply: Fix maintenance charge table kernel-doc (git-fixes).\n- power: supply: generic-adc-battery: Fix temperature IIO channel conversion (git-fixes).\n- powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved (bsc#1268315 ltc#217645).\n- powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard (bsc#1215199).\n- printk: Handle pre-enabled consoles in the top-level register_console() (bsc#1285989).\n- pseries/plpks: clear SED key data after use (bsc#1215199).\n- pseries/plpks: clear sensitive PLPKS buffers (bsc#1215199).\n- pseries/plpks: clear signed update authentication buffer (bsc#1215199).\n- pseries/plpks: fix error handling in plpks_read_var() (bsc#1215199).\n- pseries/plpks: make narrowing conversions explicit (bsc#1215199).\n- pseries/plpks: validate input to plpks_signed_update_var() (bsc#1215199).\n- regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (git-fixes).\n- regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 (git-fixes).\n- sched/debug: Change SCHED_WARN_ON() to WARN_ON_ONCE() (jsc#PED-14958 bsc#1234634 (Scheduler functional and performance\n  backports SL-16.1) bsc#1282005).\n- sched/eevdf: Update se-\u003evprot in reweight_entity() (bsc#1234634 (Scheduler functional and performance backports\n  SL-16.1) bsc#1282005).\n- sched/fair: Revert 6d71a9c61604 (\"sched/fair: Fix EEVDF entity placement bug causing scheduling lag\") (bsc#1234634\n  (Scheduler functional and performance backports SL-16.1) bsc#1282005).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- tools/hv: fix typo \"retrive\" in comment (git-fixes).\n- tools: gpio: fix building from the top level with O= (git-fixes).\n- tpm: Initialize name_size_alg for non-NULL name in tpm_buf_append_name() (stable-fixes).\n- usb: f81604: fix struct f81604_int_data size mismatch (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- wifi: ath9k: reject short WMI command responses (git-fixes).\n- wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: atk9k: Revert \"wifi: ath9k: reject short WMI command responses\" (stable-fixes).\n- wifi: brcmfmac: fix P2P device removal race in brcmf_detach() (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: keep fallback association elements alive (git-fixes).\n- wifi: mac80211: keep paired old chanctx alive (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: reject invalid 320 MHz CSA bandwidth (git-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mt76: mt792x: pick the SAR table layout from the table itself (git-fixes).\n- wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit (git-fixes).\n- wifi: mt76: mt7915: disable rx napi when removing device (git-fixes).\n- wifi: mt76: mt7925: don't put the band auto marker in TGID (git-fixes).\n- wifi: mt76: mt7925: restore the legacy BSS after MLO teardown (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wifi: wlcore: Fix runtime PM leak in wlcore_remove() (git-fixes).\n- x86/bugs: Adapt SRSO mitigation to Zen6 (bsc#1282615).\n- x86/bugs: Add attack vector controls for VMSCAPE (git-fixes).\n- x86/bugs: Remove dead code which might prevent from building (git-fixes).\n- x86/bugs: Remove uses of cpu_mitigations_off() (git-fixes).\n- x86/bugs: Remove X86_BUG_MMIO_UNKNOWN (git-fixes).\n- x86/bugs: Simplify SSB cmdline parsing (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2 (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2_user (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/mm: Drop unnecessary PMD page copy when freeing (git-fixes).\n","status":"published","published":"2026-10-24T11:28:39Z","modified":"2026-10-30T17:23:18.00959608Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24437-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-2026-31731: thermal: core: Address thermal zone removal races with resume (bsc#1264042).\n- CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests (bsc#1267430).\n- CVE-2026-53108: powerpc/64s: Fix unmap race with PMD migration entries (bsc#1269561).\n- CVE-2026-63830: net: skmsg: preserve sg.copy across SG transforms (bsc#1272178).\n- CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1273764).\n- CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback (bsc#1272898).\n- CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling (bsc#1272901).\n- CVE-2026-64062: netfs: Fix potential deadlock in write-through mode (bsc#1272952).\n- CVE-2026-64063: netfs: Fix streaming write being overwritten (bsc#1272955).\n- CVE-2026-64064: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (bsc#1272956).\n- CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs (bsc#1272509).\n- CVE-2026-64116: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (bsc#1273751).\n- CVE-2026-64280: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() (bsc#1273599).\n- CVE-2026-64424: netpoll: fix a use-after-free on shutdown path (bsc#1274256).\n- CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path (bsc#1274039).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64461: PCI: mediatek: Fix IRQ domain leak when port fails to enable (bsc#1273865).\n- CVE-2026-68233: drm/vc4: Shut down BO cache timer before teardown (bsc#1275644).\n- CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop (bsc#1275785).\n- CVE-2026-68242: drm/i915/gt: Fix NULL deref on sched_engine alloc failure (bsc#1275786).\n- CVE-2026-68323: tipc: serialize udp bearer replicast list updates (bsc#1274653).\n- CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list (bsc#1276791).\n- CVE-2026-72040: ipmi: fix refcount leak in i_ipmi_request() (bsc#1276836).\n- CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send (bsc#1275510).\n- CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB (bsc#1277174).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72172: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE (bsc#1277691).\n- CVE-2026-72174: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() (bsc#1277695).\n- CVE-2026-72212: mm/memory_hotplug: fix incorrect altmap passing in error path (bsc#1277602).\n- CVE-2026-72213: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch (bsc#1277603).\n- CVE-2026-72236: s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (bsc#1277614).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72305: VDUSE: avoid leaking information to userspace (bsc#1277747).\n- CVE-2026-72319: ipvs: fix PMTU for GUE/GRE tunnel ICMP errors (bsc#1275964).\n- CVE-2026-72355: netfs: Fix barriering when walking subrequest list (bsc#1276330).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72493: net: serialize netif_running() check in enqueue_to_backlog() (bsc#1276951).\n- CVE-2026-74306: vfio/qat: fix f_pos race in qat_vf_resume_write() (bsc#1276907).\n- CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths (bsc#1276873).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal (bsc#1278232).\n- CVE-2026-74544: net/sched: cls_u32: validate offshift to prevent shift-out-of-bounds (bsc#1277894).\n- CVE-2026-74578: crypto: algif_skcipher - force synchronous processing (bsc#1275564).\n- CVE-2026-74583: net/sched: cls_route: fix fastmap use-after-free on filter (bsc#1277889).\n- CVE-2026-74587: sctp: fix use-after-free of cached ASCONF chunk (bsc#1277821).\n- CVE-2026-74611: tls: rx: restore msg_iter before TLS 1.3 optimistic retry (bsc#1277804).\n- CVE-2026-74614: vsock/virtio: read virtqueues under worker locks (bsc#1277931).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: bpf: Fix netns reference imbalance in conntrack kfuncs (bsc#1277890).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80893: mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork() (bsc#1279706).\n- CVE-2026-80977: net: skbuff: don't touch shared zerocopy state in skb_tx_error() (bsc#1280259).\n- CVE-2026-89528: svcrdma: Reject Read lists that exceed the page budget (bsc#1280743).\n- CVE-2026-89558: md/raid10: fix still_degraded being inverted in raid10_sync_request() (bsc#1280552).\n- CVE-2026-89593: hugetlb: only adjust reservation during unmapping if mapcount is 0 (bsc#1280229).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89754: mm/pagewalk: fix stale walk-\u003eaction escaping walk_pmd_range() (bsc#1280769).\n- CVE-2026-89755: mm/migrate_device: clear stale mapping after freeing swapcache (bsc#1280770).\n- CVE-2026-89778: isofs: fix out-of-bounds page array access on empty zisofs block (bsc#1280966).\n- CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (bsc#1281144).\n- CVE-2026-89987: mm/huge_memory: transfer the pmd dirty bit to the folio on zap (bsc#1281819).\n- CVE-2026-90011: scsi: target: iscsi: Reserve a terminator byte for the login payload (bsc#1281280).\n- CVE-2026-90283: hugetlbfs: release subpool on fill_super failure (bsc#1281771).\n- CVE-2026-90289: drm/amd/display: Resize MST HDCP per-connector arrays to 32 (bsc#1281726).\n- CVE-2026-93066: x86/mm/pat: Take cpa_lock around large-page collapse (bsc#1282274).\n- CVE-2026-93134: printk: Fix possible console use-after-free (bsc#1281162).\n- CVE-2026-93222: signal: avoid shared siginfo namespace rewrites (bsc#1282742).\n- CVE-2026-93252: ocfs2: fix circular locking dependency in ocfs2_init_acl() (bsc#1282784).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access (bsc#1283037).\n- CVE-2026-97415: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (bsc#1282768).\n- CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() (bsc#1282770).\n- CVE-2026-97491: net/rds: Don't sleep inside rds_ib_conn_path_shutdown (bsc#1283142).\n- CVE-2026-97533: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (bsc#1283454).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97555: smb: client: fix heap overflow in DACL owner/group rewrite (bsc#1283851).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97564: smb: client: reject userspace cifs.idmap descriptions (bsc#1283946).\n- CVE-2026-97942: x86/alternatives: Exclude text poking against change_page_attr() (bsc#1283153).\n- CVE-2026-97943: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (bsc#1283158).\n- CVE-2026-97945: x86/mm: Fix user-space data loss with MADV_FREE and THP (bsc#1283144).\n- CVE-2026-98010: net/sched: drr: clamp quantum in change class (bsc#1283823).\n- CVE-2026-98015: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (bsc#1283963).\n- CVE-2026-98016: net/mlx5e: Fix use-after-free race in sample_restore_put() (bsc#1283894).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98077: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() (bsc#1283979).\n- CVE-2026-98089: bonding: alb: fix uninitialized transport header access in alb_determine_nd() (bsc#1283936).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98130: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (bsc#1283835).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98171: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (bsc#1284419).\n- CVE-2026-98173: smb: client: fix use-after-free of iface in cifs_try_adding_channels() (bsc#1284415).\n- CVE-2026-98174: smb: client: fix rlist race and missing initialization (bsc#1284412).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98216: IB/hfi1: Fix the PIO_CRED credit-return mmap (bsc#1284559).\n- CVE-2026-98252: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() (bsc#1284581).\n- CVE-2026-98253: RDMA/ucma: Serialize join and leave on copy_to_user failure (bsc#1284790).\n- CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread() (bsc#1284408).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98269: btrfs: abort transaction on failure to update inode for hole punching and reflinking (bsc#1284606).\n- CVE-2026-98273: x86/kprobes: Fix crash when probing CS CALL instructions (bsc#1284462).\n- CVE-2026-98323: RDMA/siw: Bound fragmented header copies by the remaining length (bsc#1284713).\n- CVE-2026-98347: IB/IPoIB: Avoid restoring OPER_UP after multicast flush (bsc#1284295).\n- CVE-2026-98352: kABI fix for RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted (bsc#1284647).\n- CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails (bsc#1284291).\n- CVE-2026-98357: IB/isert: wait for deferred control PDU completions before releasing the connection (bsc#1284791).\n- CVE-2026-98358: IB/iser: reject a remote invalidation of an unregistered direction (bsc#1284289).\n- CVE-2026-98359: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed (bsc#1284746).\n- CVE-2026-98360: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds (bsc#1284649).\n- CVE-2026-98365: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access (bsc#1284288).\n- CVE-2026-98366: RDMA/rxe: validate access flags before swapping the MR's PD (bsc#1284655).\n- CVE-2026-98367: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept (bsc#1284424).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-99999: ipv4: validate checksum_start before completing checksum (bsc#1285684).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems (git-fixes).\n- arm64: cpufeature: Make PMUVer and PerfMon unsigned (git-fixes).\n- arm64: errata: Add Cortex-A725 erratum 3821522 workaround (git-fixes) Enable workaround by default for aarch64.\n- arm64: errata: Factor out broken AMU const counter cap (git-fixes) Enable this workaround by default for aarch64.\n- arm64: errata: Workaround for SI L1 downstream coherency issue (git-fixes) Enable workaround by default for aarch64.\n- arm64: irq: exclude the softirq stack switch from KCOV (git-fixes).\n- ASoC: adau1372: allow sleepy powerdown GPIOs (git-fixes).\n- ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: cs42l52: Fix the NG Type Switch bit (git-fixes).\n- ASoC: cs42l56: Put the Limiter Cushion control on the limiter register (git-fixes).\n- ASoC: Intel: avs: Reset the stream unless it is already prepared (git-fixes).\n- ASoC: max98371: Fix the Speaker DHT Min Volume bits (git-fixes).\n- ASoC: nau8822: Fix the 128x oversampling switch bits (git-fixes).\n- ASoC: pcm3168a: Fix the DAC zero flag polarity bit (git-fixes).\n- ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM (git-fixes).\n- ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data (stable-fixes).\n- ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality (stable-fixes).\n- ASoC: stm32: spdifrx: fix synchronization state check (git-fixes).\n- ASoC: wm8978: Fix the 128x oversampling switch bits (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btintel_pcie: Add shared HW reset for clean start (git-fixes).\n- Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() (git-fixes).\n- Bluetooth: btintel_pcie: fix TX descriptor bounds check (git-fixes).\n- Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() (git-fixes).\n- Bluetooth: btintel_pcie: use managed IRQ teardown (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Serialize ACL scheduling with channel deletion (git-fixes).\n- Bluetooth: hci_core: Serialize fragmented ISO packet queueing (git-fixes).\n- Bluetooth: hci_sock: Serialize dead-device detachment (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: ISO: Reject concurrent BIS listener setup (git-fixes).\n- Bluetooth: ISO: Serialize concurrent connect calls (git-fixes).\n- Bluetooth: MGMT: Fix status of pending commands flushed on power off (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown (git-fixes).\n- Bluetooth: RFCOMM: free the skb when the DLC has no owner (git-fixes).\n- Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() (git-fixes).\n- crypto: ccp - Add support for PCI device 0x17D8 (jsc#PED-13872).\n- Drivers: hv: Avoid infinite retry loop in init_vp_index() (git-fixes).\n- Drivers: hv: Don't reset VMBus connection state on error/exit paths (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- Drivers: hv: vmbus: fix typo \"substract\" in comment (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set (git-fixes).\n- drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks (git-fixes).\n- drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr (git-fixes).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdkfd: align SDMA doorbell base for shader doorbell writes (git-fixes).\n- drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info (git-fixes).\n- drm/aspeed: Balance the display clock enable on teardown (git-fixes).\n- drm/dp: don't mark the AUX backlight enabled when enabling failed (git-fixes).\n- drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN (git-fixes).\n- drm/gud: don't keep a connector without a CRTC as connector_state (git-fixes).\n- drm/i915/gem: Prevent overstepping exec array boundary (git-fixes).\n- drm/i915/gt: Unmask interrupts only when ACTIVE is true (git-fixes).\n- drm/imagination: Fix reference and vm_bo handling in remap() (git-fixes).\n- drm/imagination: Size page table preallocation by device address (git-fixes).\n- drm/vc4: drain the hangcheck timer and works on V3D unbind (git-fixes).\n- drm/vc4: Fix binner slot allocation failing on an idle GPU (git-fixes).\n- drm/vc4: Free the BO cache size list on teardown (git-fixes).\n- drm/vc4: hdmi: Move packet RAM enable to PM runtime (git-fixes).\n- drm/vc4: Make v3d paths unavailable on any generation newer than vc4 (stable-fixes).\n- gpio: exar: initialize the ID before registering its cleanup (git-fixes).\n- gpio: xilinx: fix runtime PM leak on request error path (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- IB/hfi1: Resolve the credit-return buffer through the send context's node (git-fixes).\n- iio: accel: kionix-kx022a: Prevent memory leak and fix state (git-fixes).\n- iio: accel: kx022a: Use cleanup.h helpers (stable-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: bu27034: simplify using guard(mutex) (stable-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: rohm-bu27034: Fix error return (git-fixes).\n- iio: light: rohm-bu27034: Fix infinite delay on error (git-fixes).\n- Input: ati_remote2 - fix type confusion in device attribute handlers (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() (git-fixes).\n- KVM: PPC: Book3S HV: Add H_VIRT mapping for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add missing mappings for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users (bsc#1215199).\n- KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls (bsc#1215199).\n- KVM: PPC: Book3S HV: Free the queue pages in error path (bsc#1215199).\n- KVM: PPC: Fix callback check in kvmppc_gsm_refresh_info (jsc#PED-11016 git-fixes).\n- KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form (bsc#1215199).\n- memstick: core: wait for request completion before freeing card (git-fixes).\n- memstick: rtsx_usb_ms: complete requests after eject instead of dropping them (git-fixes).\n- mmc: cavium-octeon: destroy slot platform devices on remove (git-fixes).\n- mmc: cavium-thunderx: destroy slot platform devices on remove (git-fixes).\n- mmc: mtk-sd: Cancel request timeout work on remove (git-fixes).\n- mmc: sdhci-sprd: disable runtime PM on remove (git-fixes).\n- net: mana: reserve RX buffer headroom to fix forwarding performance (git-fixes).\n- net: usb: ax88179_178a: fix rx frame length for non-last packets (git-fixes).\n- net: usb: qmi_wwan: add Quectel EG120K-EA (stable-fixes).\n- PCI: hv: Probe vPCI buses asynchronously (git-fixes).\n- PCI: hv: Warn when wait_for_response() waits indefinitely (git-fixes).\n- pinctrl: amd: Clear S4 wake bits when firmware has _AEI (git-fixes).\n- pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 (git-fixes).\n- pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 (git-fixes).\n- power: supply: ds2780: Fix ds2780_get_capacity() returning raw value (git-fixes).\n- power: supply: Fix maintenance charge table kernel-doc (git-fixes).\n- power: supply: generic-adc-battery: Fix temperature IIO channel conversion (git-fixes).\n- powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved (bsc#1268315 ltc#217645).\n- powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard (bsc#1215199).\n- printk: Handle pre-enabled consoles in the top-level register_console() (bsc#1285989).\n- pseries/plpks: clear SED key data after use (bsc#1215199).\n- pseries/plpks: clear sensitive PLPKS buffers (bsc#1215199).\n- pseries/plpks: clear signed update authentication buffer (bsc#1215199).\n- pseries/plpks: fix error handling in plpks_read_var() (bsc#1215199).\n- pseries/plpks: make narrowing conversions explicit (bsc#1215199).\n- pseries/plpks: validate input to plpks_signed_update_var() (bsc#1215199).\n- regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (git-fixes).\n- regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 (git-fixes).\n- sched/debug: Change SCHED_WARN_ON() to WARN_ON_ONCE() (jsc#PED-14958 bsc#1234634 (Scheduler functional and performance\n  backports SL-16.1) bsc#1282005).\n- sched/eevdf: Update se-\u003evprot in reweight_entity() (bsc#1234634 (Scheduler functional and performance backports\n  SL-16.1) bsc#1282005).\n- sched/fair: Revert 6d71a9c61604 (\"sched/fair: Fix EEVDF entity placement bug causing scheduling lag\") (bsc#1234634\n  (Scheduler functional and performance backports SL-16.1) bsc#1282005).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- tools/hv: fix typo \"retrive\" in comment (git-fixes).\n- tools: gpio: fix building from the top level with O= (git-fixes).\n- tpm: Initialize name_size_alg for non-NULL name in tpm_buf_append_name() (stable-fixes).\n- usb: f81604: fix struct f81604_int_data size mismatch (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- wifi: ath9k: reject short WMI command responses (git-fixes).\n- wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: atk9k: Revert \"wifi: ath9k: reject short WMI command responses\" (stable-fixes).\n- wifi: brcmfmac: fix P2P device removal race in brcmf_detach() (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: keep fallback association elements alive (git-fixes).\n- wifi: mac80211: keep paired old chanctx alive (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: reject invalid 320 MHz CSA bandwidth (git-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mt76: mt792x: pick the SAR table layout from the table itself (git-fixes).\n- wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit (git-fixes).\n- wifi: mt76: mt7915: disable rx napi when removing device (git-fixes).\n- wifi: mt76: mt7925: don't put the band auto marker in TGID (git-fixes).\n- wifi: mt76: mt7925: restore the legacy BSS after MLO teardown (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wifi: wlcore: Fix runtime PM leak in wlcore_remove() (git-fixes).\n- x86/bugs: Adapt SRSO mitigation to Zen6 (bsc#1282615).\n- x86/bugs: Add attack vector controls for VMSCAPE (git-fixes).\n- x86/bugs: Remove dead code which might prevent from building (git-fixes).\n- x86/bugs: Remove uses of cpu_mitigations_off() (git-fixes).\n- x86/bugs: Remove X86_BUG_MMIO_UNKNOWN (git-fixes).\n- x86/bugs: Simplify SSB cmdline parsing (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2 (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2_user (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/mm: Drop unnecessary PMD page copy when freeing (git-fixes).\n","status":"published","published":"2026-10-24T11:15:59Z","modified":"2026-11-01T17:23:26.434224726Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24446-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-2026-31731: thermal: core: Address thermal zone removal races with resume (bsc#1264042).\n- CVE-2026-46028: crypto: algif_aead - snapshot IV for async AEAD requests (bsc#1267430).\n- CVE-2026-53108: powerpc/64s: Fix unmap race with PMD migration entries (bsc#1269561).\n- CVE-2026-63830: net: skmsg: preserve sg.copy across SG transforms (bsc#1272178).\n- CVE-2026-64012: net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1273764).\n- CVE-2026-64058: netfs: Fix netfs_read_folio() to wait on writeback (bsc#1272898).\n- CVE-2026-64060: netfs: Fix leak of request in netfs_write_begin() error handling (bsc#1272901).\n- CVE-2026-64062: netfs: Fix potential deadlock in write-through mode (bsc#1272952).\n- CVE-2026-64063: netfs: Fix streaming write being overwritten (bsc#1272955).\n- CVE-2026-64064: netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (bsc#1272956).\n- CVE-2026-64068: netfs: Fix missing locking around retry adding new subreqs (bsc#1272509).\n- CVE-2026-64116: ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (bsc#1273751).\n- CVE-2026-64280: fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() (bsc#1273599).\n- CVE-2026-64424: netpoll: fix a use-after-free on shutdown path (bsc#1274256).\n- CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path (bsc#1274039).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64461: PCI: mediatek: Fix IRQ domain leak when port fails to enable (bsc#1273865).\n- CVE-2026-68233: drm/vc4: Shut down BO cache timer before teardown (bsc#1275644).\n- CVE-2026-68241: drm/i915/mst: limit DP MST ESI service loop (bsc#1275785).\n- CVE-2026-68242: drm/i915/gt: Fix NULL deref on sched_engine alloc failure (bsc#1275786).\n- CVE-2026-68323: tipc: serialize udp bearer replicast list updates (bsc#1274653).\n- CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list (bsc#1276791).\n- CVE-2026-72040: ipmi: fix refcount leak in i_ipmi_request() (bsc#1276836).\n- CVE-2026-72041: espintcp: use sk_msg_free_partial to fix partial send (bsc#1275510).\n- CVE-2026-72081: scsi: elx: efct: Fix I/O leak on unsupported additional CDB (bsc#1277174).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72172: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE (bsc#1277691).\n- CVE-2026-72174: fs/proc/task_mmu: fix hugetlb self-deadlock in pagemap_scan_pte_hole() (bsc#1277695).\n- CVE-2026-72212: mm/memory_hotplug: fix incorrect altmap passing in error path (bsc#1277602).\n- CVE-2026-72213: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch (bsc#1277603).\n- CVE-2026-72236: s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (bsc#1277614).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72305: VDUSE: avoid leaking information to userspace (bsc#1277747).\n- CVE-2026-72319: ipvs: fix PMTU for GUE/GRE tunnel ICMP errors (bsc#1275964).\n- CVE-2026-72355: netfs: Fix barriering when walking subrequest list (bsc#1276330).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72493: net: serialize netif_running() check in enqueue_to_backlog() (bsc#1276951).\n- CVE-2026-74306: vfio/qat: fix f_pos race in qat_vf_resume_write() (bsc#1276907).\n- CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths (bsc#1276873).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal (bsc#1278232).\n- CVE-2026-74544: net/sched: cls_u32: validate offshift to prevent shift-out-of-bounds (bsc#1277894).\n- CVE-2026-74578: crypto: algif_skcipher - force synchronous processing (bsc#1275564).\n- CVE-2026-74583: net/sched: cls_route: fix fastmap use-after-free on filter (bsc#1277889).\n- CVE-2026-74587: sctp: fix use-after-free of cached ASCONF chunk (bsc#1277821).\n- CVE-2026-74611: tls: rx: restore msg_iter before TLS 1.3 optimistic retry (bsc#1277804).\n- CVE-2026-74614: vsock/virtio: read virtqueues under worker locks (bsc#1277931).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: bpf: Fix netns reference imbalance in conntrack kfuncs (bsc#1277890).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80893: mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork() (bsc#1279706).\n- CVE-2026-80977: net: skbuff: don't touch shared zerocopy state in skb_tx_error() (bsc#1280259).\n- CVE-2026-89528: svcrdma: Reject Read lists that exceed the page budget (bsc#1280743).\n- CVE-2026-89558: md/raid10: fix still_degraded being inverted in raid10_sync_request() (bsc#1280552).\n- CVE-2026-89593: hugetlb: only adjust reservation during unmapping if mapcount is 0 (bsc#1280229).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89754: mm/pagewalk: fix stale walk-\u003eaction escaping walk_pmd_range() (bsc#1280769).\n- CVE-2026-89755: mm/migrate_device: clear stale mapping after freeing swapcache (bsc#1280770).\n- CVE-2026-89778: isofs: fix out-of-bounds page array access on empty zisofs block (bsc#1280966).\n- CVE-2026-89811: drm/amdkfd: Add TLB flush after MES queue eviction/suspension (bsc#1281144).\n- CVE-2026-89987: mm/huge_memory: transfer the pmd dirty bit to the folio on zap (bsc#1281819).\n- CVE-2026-90011: scsi: target: iscsi: Reserve a terminator byte for the login payload (bsc#1281280).\n- CVE-2026-90283: hugetlbfs: release subpool on fill_super failure (bsc#1281771).\n- CVE-2026-90289: drm/amd/display: Resize MST HDCP per-connector arrays to 32 (bsc#1281726).\n- CVE-2026-93066: x86/mm/pat: Take cpa_lock around large-page collapse (bsc#1282274).\n- CVE-2026-93134: printk: Fix possible console use-after-free (bsc#1281162).\n- CVE-2026-93222: signal: avoid shared siginfo namespace rewrites (bsc#1282742).\n- CVE-2026-93252: ocfs2: fix circular locking dependency in ocfs2_init_acl() (bsc#1282784).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93806: wifi: cfg80211: validate assoc response length before status and IE access (bsc#1283037).\n- CVE-2026-97415: btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (bsc#1282768).\n- CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() (bsc#1282770).\n- CVE-2026-97491: net/rds: Don't sleep inside rds_ib_conn_path_shutdown (bsc#1283142).\n- CVE-2026-97533: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (bsc#1283454).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97555: smb: client: fix heap overflow in DACL owner/group rewrite (bsc#1283851).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97564: smb: client: reject userspace cifs.idmap descriptions (bsc#1283946).\n- CVE-2026-97942: x86/alternatives: Exclude text poking against change_page_attr() (bsc#1283153).\n- CVE-2026-97943: x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (bsc#1283158).\n- CVE-2026-97945: x86/mm: Fix user-space data loss with MADV_FREE and THP (bsc#1283144).\n- CVE-2026-98010: net/sched: drr: clamp quantum in change class (bsc#1283823).\n- CVE-2026-98015: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (bsc#1283963).\n- CVE-2026-98016: net/mlx5e: Fix use-after-free race in sample_restore_put() (bsc#1283894).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98077: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() (bsc#1283979).\n- CVE-2026-98089: bonding: alb: fix uninitialized transport header access in alb_determine_nd() (bsc#1283936).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98130: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (bsc#1283835).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98171: smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (bsc#1284419).\n- CVE-2026-98173: smb: client: fix use-after-free of iface in cifs_try_adding_channels() (bsc#1284415).\n- CVE-2026-98174: smb: client: fix rlist race and missing initialization (bsc#1284412).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98216: IB/hfi1: Fix the PIO_CRED credit-return mmap (bsc#1284559).\n- CVE-2026-98252: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() (bsc#1284581).\n- CVE-2026-98253: RDMA/ucma: Serialize join and leave on copy_to_user failure (bsc#1284790).\n- CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread() (bsc#1284408).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98269: btrfs: abort transaction on failure to update inode for hole punching and reflinking (bsc#1284606).\n- CVE-2026-98273: x86/kprobes: Fix crash when probing CS CALL instructions (bsc#1284462).\n- CVE-2026-98323: RDMA/siw: Bound fragmented header copies by the remaining length (bsc#1284713).\n- CVE-2026-98347: IB/IPoIB: Avoid restoring OPER_UP after multicast flush (bsc#1284295).\n- CVE-2026-98352: kABI fix for RDMA/rtrs-clt: Fix CQ pool leak when connect is interrupted (bsc#1284647).\n- CVE-2026-98354: RDMA/mad: Fix receive buffer leak when PKey enforcement fails (bsc#1284291).\n- CVE-2026-98357: IB/isert: wait for deferred control PDU completions before releasing the connection (bsc#1284791).\n- CVE-2026-98358: IB/iser: reject a remote invalidation of an unregistered direction (bsc#1284289).\n- CVE-2026-98359: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed (bsc#1284746).\n- CVE-2026-98360: RDMA/rxe: insert mcg into mcg_tree only after rxe_mcast_add() succeeds (bsc#1284649).\n- CVE-2026-98365: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access (bsc#1284288).\n- CVE-2026-98366: RDMA/rxe: validate access flags before swapping the MR's PD (bsc#1284655).\n- CVE-2026-98367: RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept (bsc#1284424).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-99999: ipv4: validate checksum_start before completing checksum (bsc#1285684).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices (git-fixes).\n- arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems (git-fixes).\n- arm64: cpufeature: Make PMUVer and PerfMon unsigned (git-fixes).\n- arm64: errata: Add Cortex-A725 erratum 3821522 workaround (git-fixes) Enable workaround by default for aarch64.\n- arm64: errata: Factor out broken AMU const counter cap (git-fixes) Enable this workaround by default for aarch64.\n- arm64: errata: Workaround for SI L1 downstream coherency issue (git-fixes) Enable workaround by default for aarch64.\n- arm64: irq: exclude the softirq stack switch from KCOV (git-fixes).\n- ASoC: adau1372: allow sleepy powerdown GPIOs (git-fixes).\n- ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: cs42l52: Fix the NG Type Switch bit (git-fixes).\n- ASoC: cs42l56: Put the Limiter Cushion control on the limiter register (git-fixes).\n- ASoC: Intel: avs: Reset the stream unless it is already prepared (git-fixes).\n- ASoC: max98371: Fix the Speaker DHT Min Volume bits (git-fixes).\n- ASoC: nau8822: Fix the 128x oversampling switch bits (git-fixes).\n- ASoC: pcm3168a: Fix the DAC zero flag polarity bit (git-fixes).\n- ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM (git-fixes).\n- ASoC: SOF: ipc4-priv: Add kernel doc for fw_context_save of sof_ipc4_fw_data (stable-fixes).\n- ASoC: SOF: ipc4/Intel: Add support for library restore firmware functionality (stable-fixes).\n- ASoC: stm32: spdifrx: fix synchronization state check (git-fixes).\n- ASoC: wm8978: Fix the 128x oversampling switch bits (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btintel_pcie: Add shared HW reset for clean start (git-fixes).\n- Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() (git-fixes).\n- Bluetooth: btintel_pcie: fix TX descriptor bounds check (git-fixes).\n- Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() (git-fixes).\n- Bluetooth: btintel_pcie: use managed IRQ teardown (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Serialize ACL scheduling with channel deletion (git-fixes).\n- Bluetooth: hci_core: Serialize fragmented ISO packet queueing (git-fixes).\n- Bluetooth: hci_sock: Serialize dead-device detachment (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: ISO: Reject concurrent BIS listener setup (git-fixes).\n- Bluetooth: ISO: Serialize concurrent connect calls (git-fixes).\n- Bluetooth: MGMT: Fix status of pending commands flushed on power off (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown (git-fixes).\n- Bluetooth: RFCOMM: free the skb when the DLC has no owner (git-fixes).\n- Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() (git-fixes).\n- crypto: ccp - Add support for PCI device 0x17D8 (jsc#PED-13872).\n- Drivers: hv: Avoid infinite retry loop in init_vp_index() (git-fixes).\n- Drivers: hv: Don't reset VMBus connection state on error/exit paths (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- Drivers: hv: vmbus: fix typo \"substract\" in comment (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/uvd3.1: Fix checking whether UVD firmware keyselect was already set (git-fixes).\n- drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks (git-fixes).\n- drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr (git-fixes).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdkfd: align SDMA doorbell base for shader doorbell writes (git-fixes).\n- drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info (git-fixes).\n- drm/aspeed: Balance the display clock enable on teardown (git-fixes).\n- drm/dp: don't mark the AUX backlight enabled when enabling failed (git-fixes).\n- drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN (git-fixes).\n- drm/gud: don't keep a connector without a CRTC as connector_state (git-fixes).\n- drm/i915/gem: Prevent overstepping exec array boundary (git-fixes).\n- drm/i915/gt: Unmask interrupts only when ACTIVE is true (git-fixes).\n- drm/imagination: Fix reference and vm_bo handling in remap() (git-fixes).\n- drm/imagination: Size page table preallocation by device address (git-fixes).\n- drm/vc4: drain the hangcheck timer and works on V3D unbind (git-fixes).\n- drm/vc4: Fix binner slot allocation failing on an idle GPU (git-fixes).\n- drm/vc4: Free the BO cache size list on teardown (git-fixes).\n- drm/vc4: hdmi: Move packet RAM enable to PM runtime (git-fixes).\n- drm/vc4: Make v3d paths unavailable on any generation newer than vc4 (stable-fixes).\n- gpio: exar: initialize the ID before registering its cleanup (git-fixes).\n- gpio: xilinx: fix runtime PM leak on request error path (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- IB/hfi1: Resolve the credit-return buffer through the send context's node (git-fixes).\n- iio: accel: kionix-kx022a: Prevent memory leak and fix state (git-fixes).\n- iio: accel: kx022a: Use cleanup.h helpers (stable-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: bu27034: simplify using guard(mutex) (stable-fixes).\n- iio: imu: adis16480: fix unprotected debugfs reads (git-fixes).\n- iio: light: rohm-bu27034: Fix error return (git-fixes).\n- iio: light: rohm-bu27034: Fix infinite delay on error (git-fixes).\n- Input: ati_remote2 - fix type confusion in device attribute handlers (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() (git-fixes).\n- KVM: PPC: Book3S HV: Add H_VIRT mapping for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add missing mappings for tracing exits (bsc#1215199).\n- KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users (bsc#1215199).\n- KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls (bsc#1215199).\n- KVM: PPC: Book3S HV: Free the queue pages in error path (bsc#1215199).\n- KVM: PPC: Fix callback check in kvmppc_gsm_refresh_info (jsc#PED-11016 git-fixes).\n- KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form (bsc#1215199).\n- memstick: core: wait for request completion before freeing card (git-fixes).\n- memstick: rtsx_usb_ms: complete requests after eject instead of dropping them (git-fixes).\n- mmc: cavium-octeon: destroy slot platform devices on remove (git-fixes).\n- mmc: cavium-thunderx: destroy slot platform devices on remove (git-fixes).\n- mmc: mtk-sd: Cancel request timeout work on remove (git-fixes).\n- mmc: sdhci-sprd: disable runtime PM on remove (git-fixes).\n- net: mana: reserve RX buffer headroom to fix forwarding performance (git-fixes).\n- net: usb: ax88179_178a: fix rx frame length for non-last packets (git-fixes).\n- net: usb: qmi_wwan: add Quectel EG120K-EA (stable-fixes).\n- PCI: hv: Probe vPCI buses asynchronously (git-fixes).\n- PCI: hv: Warn when wait_for_response() waits indefinitely (git-fixes).\n- pinctrl: amd: Clear S4 wake bits when firmware has _AEI (git-fixes).\n- pinctrl: qcom: ipq5018: add missing pwm3 function on gpio13 (git-fixes).\n- pinctrl: qcom: ipq5018: replace gcc_plltest with pwm2 on gpio12 (git-fixes).\n- power: supply: ds2780: Fix ds2780_get_capacity() returning raw value (git-fixes).\n- power: supply: Fix maintenance charge table kernel-doc (git-fixes).\n- power: supply: generic-adc-battery: Fix temperature IIO channel conversion (git-fixes).\n- powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved (bsc#1268315 ltc#217645).\n- powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard (bsc#1215199).\n- printk: Handle pre-enabled consoles in the top-level register_console() (bsc#1285989).\n- pseries/plpks: clear SED key data after use (bsc#1215199).\n- pseries/plpks: clear sensitive PLPKS buffers (bsc#1215199).\n- pseries/plpks: clear signed update authentication buffer (bsc#1215199).\n- pseries/plpks: fix error handling in plpks_read_var() (bsc#1215199).\n- pseries/plpks: make narrowing conversions explicit (bsc#1215199).\n- pseries/plpks: validate input to plpks_signed_update_var() (bsc#1215199).\n- regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (git-fixes).\n- regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 (git-fixes).\n- sched/debug: Change SCHED_WARN_ON() to WARN_ON_ONCE() (jsc#PED-14958 bsc#1234634 (Scheduler functional and performance\n  backports SL-16.1) bsc#1282005).\n- sched/eevdf: Update se-\u003evprot in reweight_entity() (bsc#1234634 (Scheduler functional and performance backports\n  SL-16.1) bsc#1282005).\n- sched/fair: Revert 6d71a9c61604 (\"sched/fair: Fix EEVDF entity placement bug causing scheduling lag\") (bsc#1234634\n  (Scheduler functional and performance backports SL-16.1) bsc#1282005).\n- smb: client: harden DFS cache against invalid target hints (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- tools/hv: fix typo \"retrive\" in comment (git-fixes).\n- tools: gpio: fix building from the top level with O= (git-fixes).\n- tpm: Initialize name_size_alg for non-NULL name in tpm_buf_append_name() (stable-fixes).\n- usb: f81604: fix struct f81604_int_data size mismatch (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- wifi: ath9k: reject short WMI command responses (git-fixes).\n- wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: atk9k: Revert \"wifi: ath9k: reject short WMI command responses\" (stable-fixes).\n- wifi: brcmfmac: fix P2P device removal race in brcmf_detach() (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: keep fallback association elements alive (git-fixes).\n- wifi: mac80211: keep paired old chanctx alive (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: reject invalid 320 MHz CSA bandwidth (git-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mt76: mt792x: pick the SAR table layout from the table itself (git-fixes).\n- wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit (git-fixes).\n- wifi: mt76: mt7915: disable rx napi when removing device (git-fixes).\n- wifi: mt76: mt7925: don't put the band auto marker in TGID (git-fixes).\n- wifi: mt76: mt7925: restore the legacy BSS after MLO teardown (git-fixes).\n- wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wifi: wlcore: Fix runtime PM leak in wlcore_remove() (git-fixes).\n- x86/bugs: Adapt SRSO mitigation to Zen6 (bsc#1282615).\n- x86/bugs: Add attack vector controls for VMSCAPE (git-fixes).\n- x86/bugs: Remove dead code which might prevent from building (git-fixes).\n- x86/bugs: Remove uses of cpu_mitigations_off() (git-fixes).\n- x86/bugs: Remove X86_BUG_MMIO_UNKNOWN (git-fixes).\n- x86/bugs: Simplify SSB cmdline parsing (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2 (git-fixes).\n- x86/bugs: Use early_param() for spectre_v2_user (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/mm: Drop unnecessary PMD page copy when freeing (git-fixes).\n","status":"published","published":"2026-10-24T11:28:39Z","modified":"2026-11-01T17:23:26.472024925Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24550-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68219: cifs: fix memory leak in smb3_fs_context_parse_param error path (bsc#1255222).\n- CVE-2026-31708: smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path (bsc#1264022).\n- CVE-2026-31709: smb: client: validate the whole DACL before rewriting it in cifsacl (bsc#1264024).\n- CVE-2026-43350: smb: client: require a full NFS mode SID before reading mode bits (bsc#1264985).\n- CVE-2026-46155: smb/client: fix out-of-bounds read in smb2_compound_op() (bsc#1267720).\n- CVE-2026-64324: udf: validate free block extents against the partition length (bsc#1273970).\n- CVE-2026-64370: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (bsc#1273805).\n- CVE-2026-64380: smb: client: harden POSIX SID length parsing (bsc#1273557).\n- CVE-2026-64413: netfilter: ebtables: zero chainstack array (bsc#1274082).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-68186: binfmt_misc: set have_execfd only once the interpreter is opened (bsc#1274949).\n- CVE-2026-68447: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size (bsc#1276280).\n- CVE-2026-72010: cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed (bsc#1276776).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72111: bpf: Reset register bounds before narrowing retval range in check_mem_access() (bsc#1277389).\n- CVE-2026-72127: netdev-genl: report NAPI thread PID in the caller's pid namespace (bsc#1277542).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72318: cifs: validate DFS referral string offsets (bsc#1275939).\n- CVE-2026-72400: seg6: validate SRH length before reading fixed fields (bsc#1278030).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72416: netfilter: nft_compat: ebtables emulation must reject non-bridge targets (bsc#1278041).\n- CVE-2026-72428: bpf: Fix stack slot index in nospec checks (bsc#1278050).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74399: evm: terminate and bound the evm_xattrs read buffer (bsc#1278319).\n- CVE-2026-74565: netfilter: nf_tables: make nft_object rhltable per table (bsc#1275568).\n- CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown (bsc#1277903).\n- CVE-2026-74620: net/sched: act_gact, act_police: range check the fallback control action (bsc#1277044).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: net: netfilter: Make ct zone opts configurable for bpf ct helpers (bsc#1277890).\n- CVE-2026-74720: bpf: Preserve pointer state for commuted arithmetic (bsc#1276574).\n- CVE-2026-74746: netfilter: flowtable: publish GC-visible tuple last (bsc#1278101).\n- CVE-2026-74748: netfilter: ipset: fix refcount race between list:set GC and swap (bsc#1277578).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80602: perf/x86/amd/lbr: Fix kernel address leakage (bsc#1278123).\n- CVE-2026-80637: netfilter: synproxy: fix unaligned memory access in timestamp adjustment (bsc#1278343).\n- CVE-2026-80684: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure (bsc#1277467).\n- CVE-2026-80709: s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs (bsc#1278202).\n- CVE-2026-80717: sctp: validate Adaptation Indication parameter length (bsc#1277836).\n- CVE-2026-80755: selinux: reject a permission value exceeding the class permission count (bsc#1278415).\n- CVE-2026-80757: selinux: reject a class permission count below its inherited common (bsc#1278711).\n- CVE-2026-80808: ext4: stop retrying saturated xattr cache entries (bsc#1279795).\n- CVE-2026-80809: ocfs2: fix missing metadata reservation for large xattrs (bsc#1279606).\n- CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX failure (bsc#1279564).\n- CVE-2026-80879: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write (bsc#1279494).\n- CVE-2026-80881: ocfs2: fix buffer head management in ocfs2_read_blocks() (bsc#1279496).\n- CVE-2026-80978: ip6_gre: fix hardware header length for NBMA tunnels (bsc#1280253).\n- CVE-2026-80988: NTB: ntb_transport: Fail TX enqueue when the QP link is down (bsc#1280266).\n- CVE-2026-89491: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() (bsc#1280472).\n- CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler (bsc#1280520).\n- CVE-2026-89495: ocfs2: bound namelen in dlm_migrate_request_handler (bsc#1280569).\n- CVE-2026-89537: SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 (bsc#1280713).\n- CVE-2026-89554: mptcp: fix uninitialized local_id in syncookie MP_JOIN reconstruction (bsc#1280736).\n- CVE-2026-89559: libnvdimm/labels: Prevent integer overflow in __nd_label_validate() (bsc#1280554).\n- CVE-2026-89560: landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation (bsc#1280806).\n- CVE-2026-89595: fsnotify: Fix stale object mask after concurrent mark updates (bsc#1280834).\n- CVE-2026-89608: ecryptfs: pass packet set buffer size to parser (bsc#1280826).\n- CVE-2026-89637: smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed secondary T2 (bsc#1280492).\n- CVE-2026-89642: cifs: call pagecache_isize_extended() in cifs_setsize() when extending (bsc#1280970).\n- CVE-2026-89649: ceph: bound xattr value length in __build_xattrs() (bsc#1280434).\n- CVE-2026-89654: ceph: fix UAF in check_new_map() on session freed during unlock (bsc#1280415).\n- CVE-2026-89655: ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock (bsc#1280398).\n- CVE-2026-89656: libceph: reject buckets with mismatched CRUSH ids (bsc#1280563).\n- CVE-2026-89657: libceph: validate OSD extent maps before cursor advance (bsc#1280545).\n- CVE-2026-89751: x86/tdx: Fix off-by-one in port I/O handling (bsc#1280822).\n- CVE-2026-89761: apparmor: fix out-of-bounds write when null terminating a label vec (bsc#1280745).\n- CVE-2026-89786: ext4: fix out-of-bounds read in ext4_read_inline_dir() (bsc#1280976).\n- CVE-2026-89787: ext4: check dir entry fits before reading the hash trailer in ext4_search_dir() (bsc#1280977).\n- CVE-2026-90042: ceph: properly decrypt filenames in vmalloc() buffers (bsc#1280948).\n- CVE-2026-90057: slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() (bsc#1281650).\n- CVE-2026-90081: net/rds: use wq_has_sleeper() in rds_cong_map_updated() (bsc#1281490).\n- CVE-2026-90092: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN (bsc#1281384).\n- CVE-2026-90103: NFSv4.2: fix LAYOUTSTATS send buffer exhaustion (bsc#1281538).\n- CVE-2026-90107: net/smc: free pending qentry in smc_llc_flow_stop() before memset (bsc#1281510).\n- CVE-2026-90114: net: bridge: Reject descending VLAN tunnel ranges (bsc#1281509).\n- CVE-2026-90128: vdpa/mlx5: fix wrong list iterated in add_direct_chain error path (bsc#1281577).\n- CVE-2026-90138: vsock: don't check the listener's sk_err in vsock_accept() (bsc#1281535).\n- CVE-2026-90148: NFSv4: Fix incorrect argument passed to nfs4_delete_lease() in nfs4_add_lease() (bsc#1281551).\n- CVE-2026-90227: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (bsc#1281705).\n- CVE-2026-90230: nvme: Add the DHCHAP maximum HD IDs (bsc#1281715).\n- CVE-2026-90393: bpf: Fix potential UAF in bpf_netns_link_update_prog (bsc#1282289).\n- CVE-2026-93054: uio: Fix stale info pointer in failed registration path (bsc#1282276).\n- CVE-2026-93228: svcrdma: Reject Write/Reply chunks with segcount 0 (bsc#1282697).\n- CVE-2026-93231: lockd: fix swapped arguments in nlmsvc_match_ip() (bsc#1282778).\n- CVE-2026-93250: vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() (bsc#1282677).\n- CVE-2026-93262: md/raid5-ppl: fix use-after-free in ppl_do_flush() (bsc#1283004).\n- CVE-2026-93795: blk-cgroup: fix leaks and online flag on radix_tree_insert failure (bsc#1283155).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93817: perf: Fix addr_filter_ranges lifetime (bsc#1283017).\n- CVE-2026-93828: exfat: fix handling of damaged volume in exfat_create_upcase_table() (bsc#1282890).\n- CVE-2026-93830: net: stmmac: xgmac2: disable RBUE in default RX interrupt mask (bsc#1282889).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97565: smb: client: reject short READ responses in CIFSSMBRead() (bsc#1283793).\n- CVE-2026-97575: media: v4l2-ctrls: validate AV1 tile counts (bsc#1283337).\n- CVE-2026-97596: ipvs: reject invalid states in connection template sync records (bsc#1283941).\n- CVE-2026-97603: idpf: disable DIM work before freeing q_vectors (bsc#1283782).\n- CVE-2026-97612: net: mpls: clear inner_protocol when the last label is popped (bsc#1283967).\n- CVE-2026-97954: net/rds: fix tcp stream corruption with large pages (bsc#1283113).\n- CVE-2026-97963: net: stmmac: initialize ptp_lock at probe time (bsc#1282984).\n- CVE-2026-97964: ppp_synctty: ensure a writeable skb header (bsc#1282962).\n- CVE-2026-97965: vxlan: initialize _md in vxlan_xmit_one() (bsc#1282963).\n- CVE-2026-97991: vdpa_sim_blk: reject out-of-range sector starts (bsc#1283356).\n- CVE-2026-97993: vhost-vdpa: don't install the eventfd_ctx_fdget() error in config_ctx (bsc#1283339).\n- CVE-2026-98014: net/mlx5: E-Switch, prevent mc_list repopulation during vport disable (bsc#1283668).\n- CVE-2026-98022: net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations (bsc#1283810).\n- CVE-2026-98023: vxlan: reject dynamic fdb entries that reference a nexthop id (bsc#1283960).\n- CVE-2026-98031: nexthop: Initialize extack in remove_nh_grp_entry() (bsc#1283662).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98068: net/rds: don't let rds_conn_shutdown() consume a concurrent drop (bsc#1283903).\n- CVE-2026-98069: net/rds: acquire the fastpath locks in rds_conn_shutdown() (bsc#1283863).\n- CVE-2026-98070: net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() (bsc#1283916).\n- CVE-2026-98071: net/rds: clear cp_flags bits individually in rds_conn_path_reset() (bsc#1283842).\n- CVE-2026-98072: net/rds: use wq_has_sleeper() in release_in_xmit() (bsc#1283846).\n- CVE-2026-98074: bonding: do not clear curr_active_slave prematurely when releasing all slaves (bsc#1283871).\n- CVE-2026-98078: ipvs: fix reversed sequence option serialization (bsc#1284150).\n- CVE-2026-98095: af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header() (bsc#1283921).\n- CVE-2026-98122: vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() (bsc#1283886).\n- CVE-2026-98124: smb/client: invalidate fscache for fallocate range operations (bsc#1283821).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98154: nvme-rdma: fix -EIO cleanup order in queue_rq (bsc#1283418).\n- CVE-2026-98158: ppp_async: drop the errored frame instead of resetting its headroom (bsc#1283933).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98257: rds: ib: use rds_conn_drop() on protocol version mismatch (bsc#1284346).\n- CVE-2026-98258: posix-cpu-timers: Prevent freeing a timer which is queued on the expiry list (bsc#1284584).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98264: ALSA: virtio: reset device before deleting virtqueues (bsc#1284363).\n- CVE-2026-98282: powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba (bsc#1284360).\n- CVE-2026-98283: KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid() (bsc#1284595).\n- CVE-2026-98306: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation (bsc#1284505).\n- CVE-2026-98368: esp: downgrade zerocopy managed frags before mutating skb frags (bsc#1284498).\n- CVE-2026-98374: tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() (bsc#1284740).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-98471: KVM: SEV: Do cache maintenance on the source VM during intra-host migration (bsc#1286240).\n- CVE-2026-98631: xsk: Use a 32-bit compare in xsk_map_gen_lookup (bsc#1286233).\n- CVE-2026-99131: xfs: fix capability check in xfs (bsc#1288668).\n- CVE-2026-100071: net: hsr: free learned nodes on device setup failure (bsc#1282870).\n\nThe following non security issues were fixed:\n\n- accel/qaic: reject BO sizes that overflow page count (git-fixes).\n- ACPI: CPPC: Validate the _CPC package header (git-fixes).\n- ACPI: extlog: Validate elog record length before walking sections (git-fixes).\n- ACPI: PCI: pci_link: clear driver_data before free (git-fixes).\n- ACPI: pfr_update: zero-initialize capability query result (git-fixes).\n- ACPI: PM: Drop parent state update from acpi_device_get_power() (git-fixes).\n- ACPI: tables: handle failed initrd override mappings (git-fixes).\n- ACPI: TAD: Rearrange RT data validation checking (stable-fixes).\n- ACPI: video: Fix backlight unregistration ordering (git-fixes).\n- ACPICA: Fix memory leak in acpi_ds_create_field() (git-fixes).\n- ACPICA: Fix PCC OperationRegion command offsets (git-fixes).\n- ACPICA: Initialize parser_state.aml_end in acpi_install_method() (git-fixes).\n- ALSA: 6fire: take stream_mutex in the Digital Thru control (git-fixes).\n- ALSA: aloop: Keep the timer source alive until card release (git-fixes).\n- ALSA: caiaq: Fix races at MIDI URB and trigger accesses (git-fixes).\n- ALSA: caiaq: Fix the Kore controller key map (git-fixes).\n- ALSA: caiaq: Register card at the final step (git-fixes).\n- ALSA: caiaq: Serialize access to the EP1 command buffer (git-fixes).\n- ALSA: compress: add missing OPEN-state gate to SET_METADATA (git-fixes).\n- ALSA: control: Fix virtual master creation reference in kernel-doc (git-fixes).\n- ALSA: cs46xx: fix unit mismatch in DSP code area bounds check (git-fixes).\n- ALSA: hda/hdmi: clamp num_cvts against cvt_nids in hdmi_read_pin_conn (git-fixes).\n- ALSA: hda/hdmi: clamp sad_count in ELD proc write handler (git-fixes).\n- ALSA: hda: Add NULL check for the driver pointer at unsol event work (git-fixes).\n- ALSA: hda: Avoid non-operational GPU warning at regular device removal (git-fixes).\n- ALSA: hda: Fix potential UAF for gating jack (git-fixes).\n- ALSA: hda: intel: Cancel delayed work at shutdown, too (git-fixes).\n- ALSA: hda: Reject codec reset on ASoC (ext_ops) buses (git-fixes).\n- ALSA: jack: Fix kctl free at error in snd_jack_kctl_new() (git-fixes).\n- ALSA: line6: Clear prev_fbuf on capture buffer release (git-fixes).\n- ALSA: line6: Fix potential OOB write in line6_capture_copy() (git-fixes).\n- ALSA: line6: Reject too small max packet sizes (git-fixes).\n- ALSA: line6: Use kzalloc() for PCM buffer allocation (git-fixes).\n- ALSA: pcm: Fix driver_tstamp value reporting (git-fixes).\n- ALSA: pcm: Protect channel-map reads against runtime detach (git-fixes).\n- ALSA: pcm: Protect the unregister notifier traversal (git-fixes).\n- ALSA: pcm: Remove channel-map controls before freeing substreams (git-fixes).\n- ALSA: pcm: Unlink substreams before releasing them (git-fixes).\n- ALSA: seq: oss: Skip events until fully initialized (git-fixes).\n- ALSA: sh: aica: Fix spu_memset() stride (git-fixes).\n- ALSA: ump: Correct return size of fill_rpn() (git-fixes).\n- ALSA: usb-audio: Use fixed control index for us16x08 mixer elements (git-fixes).\n- ALSA: via82xx: use helper to activate DXS controls (git-fixes).\n- ASoC: adau17x1: return cache sync errors from resume (git-fixes).\n- ASoC: ak4642: return cache sync errors from resume (git-fixes).\n- ASoC: amd: acp: Fix .close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_sdw_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix acp3x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix memory leak in acp3x_dma_close() (git-fixes).\n- ASoC: amd: renoir: Fix acp_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: vangogh: Fix acp5x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: amd: yc: Fix acp6x_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: arizona-jack: Fix runtime PM imbalance in arizona_start_hpdet_acc_id() (git-fixes).\n- ASoC: atmel-i2s: fix MCK generator error handling (git-fixes).\n- ASoC: atmel-i2s: use optional API for gclk (git-fixes).\n- ASoC: atmel-i2s: use optional API for muxclk (git-fixes).\n- ASoC: atmel: atmel-pcm-pdc: Fix atmel_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: codecs: da732x: Fix definition of ADC2 EQ Overall Volume control (git-fixes).\n- ASoC: codecs: es*: Modify the registers related to ALC RECOVERY (git-fixes).\n- ASoC: codecs: rt5659: propagate GPIO errors (git-fixes).\n- ASoC: codecs: rt5682s: disable jack detection work on shutdown (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: tlv320adc3xxx: Fix definition of AGC Target Level control (git-fixes).\n- ASoC: codecs: wcd9335: Fix SLIM interface device leak in wcd9335_slim_status() (git-fixes).\n- ASoC: codecs: wm5100: Fix definition of EQ3 Band 1 Volume control (git-fixes).\n- ASoC: codecs: wm8510: Fix definition of ADC Inversion Switch control (git-fixes).\n- ASoC: codecs: wm8737: Fix definition of zero cross switches (git-fixes).\n- ASoC: codecs: wm8750: Fix definition of ALC Capture NG Type control (git-fixes).\n- ASoC: codecs: wm8955: Fix definition of Treble Cutoff control (git-fixes).\n- ASoC: codecs: wm8983: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8985: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8994: Fix definition of WM8958 noise gate hold time controls (git-fixes).\n- ASoC: codecs: wm8994: Fix runtime PM leak in wm8994_mic_detect() (git-fixes).\n- ASoC: codecs: wm_hubs: Fix definition of MIXINR to MIXOUTR volume control (git-fixes).\n- ASoC: codecs: wsa883x: disable runtime PM on unbind (git-fixes).\n- ASoC: codecs: wsa884x: disable runtime PM on unbind (git-fixes).\n- ASoC: cs42l56: Remove the ADC Mute Switch control (git-fixes).\n- ASoC: es8316: return cache sync errors from resume (git-fixes).\n- ASoC: fsl_asrc: check the second front-end DMA channel (git-fixes).\n- ASoC: fsl_asrc: use regmap_write_bits to update clock source registers (git-fixes).\n- ASoC: hdac_hda: Balance the runtime PM disable in codec remove (git-fixes).\n- ASoC: hdac_hda: Keep runtime PM state in sync across codec remove/probe (git-fixes).\n- ASoC: hdac_hda: Restore the codec device type on unbind (git-fixes).\n- ASoC: imx-pcm-rpmsg: Fix imx_rpmsg_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: intel: atom: Fix .shutdown() being skipped on rollback (git-fixes).\n- ASoC: Intel: atom: Fix platform device leak on probe failure (git-fixes).\n- ASoC: Intel: avs: Prevent module info underflow (git-fixes).\n- ASoC: Intel: avs: Unprepare a stream when recovery occurs (git-fixes).\n- ASoC: mediatek: common: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt6797: fix wrong unwind order and error code in enable_clock (git-fixes).\n- ASoC: mediatek: mt8183: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8183: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8183: Fix wrong clock cleanup on clk_set_parent() failure (git-fixes).\n- ASoC: mediatek: mt8186: Fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL mux setting error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8186: Fix MCK error handling (git-fixes).\n- ASoC: mediatek: mt8188: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle tuner clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Propagate regmap update errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-pcm: Handle runtime resume errors (git-fixes).\n- ASoC: mediatek: mt8192-mt6359: Fix error handling in MTKAIF calibration (git-fixes).\n- ASoC: mediatek: mt8192: check return values in mt8192_afe_gpio_init() (git-fixes).\n- ASoC: mediatek: mt8192: fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix APLL mux error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix error handling in APLL enable functions (git-fixes).\n- ASoC: mediatek: mt8192: fix MCK clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: Handle regcache_sync() failure in runtime resume (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in TDM DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate mt8192_afe_gpio_request() errors in ADDA DAI (git-fixes).\n- ASoC: mediatek: mt8192: switch to devm_clk_get_optional() (git-fixes).\n- ASoC: mediatek: mt8195: Check paired MEMIF clock enable in FE trigger (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM MCLK error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM probe error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix FE startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix HDMI TX startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix main clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix paired memif clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix register access clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix runtime resume error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix timing system clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix tuner clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Propagate IRQ lookup errors (git-fixes).\n- ASoC: mt6359-accdet: manage private workqueues with devres (git-fixes).\n- ASoC: nau8540: return cache sync errors from resume (git-fixes).\n- ASoC: ops: Fix return value in snd_soc_limit_volume() (git-fixes).\n- ASoC: qcom: q6apm: clear g_apm on driver removal (git-fixes).\n- ASoC: qcom: qdsp6: q6afe: fix clk vote response type mismatch (git-fixes).\n- ASoC: rockchip: rockchip_i2s: Handle runtime PM resume failures in set_fmt (git-fixes).\n- ASoC: rt711-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt711-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: rt712-sdca-dmic: fix drvdata type in the gain controls (git-fixes).\n- ASoC: rt712-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt722-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt1011: return cache sync errors from resume (git-fixes).\n- ASoC: rt1016: return cache sync errors from resume (git-fixes).\n- ASoC: rt1305: return cache sync errors from resume (git-fixes).\n- ASoC: rt1308: return cache sync errors from resume (git-fixes).\n- ASoC: rt5616: return cache sync errors from resume (git-fixes).\n- ASoC: rt5659: return cache sync errors from resume (git-fixes).\n- ASoC: rt5660: return cache sync errors from resume (git-fixes).\n- ASoC: rt5665: return cache sync errors from resume (git-fixes).\n- ASoC: rt5682-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: soc-ac97: Fix error handling in snd_soc_new_ac97_component() (git-fixes).\n- ASoC: soc-component: Fix return type of snd_soc_pcm_component_pointer() (git-fixes).\n- ASoC: ti: davinci-mcasp: Fix runtime PM imbalance in __davinci_mcasp_set_clkdiv() (git-fixes).\n- ASoC: wcd9335: Fix device reference leak in wcd9335_slim_status() (git-fixes).\n- ASoC: wcd-mbhc-v2: Fix incorrect properties names and typos (git-fixes).\n- ASoC: wm8994: don't lose the AIF clock ratio when staying at 32kHz SYSCLK (git-fixes).\n- ASoC: wm8994: fix MCLK gating for AIF clocks sourced from MCLK2 (git-fixes).\n- ASoC: wm8994: fix MCLK index used for setting MCLK rate (git-fixes).\n- ASoC: wm8994: Fix runtime PM imbalance in wm8994_component_probe() (git-fixes).\n- ASoC: wm8994: follow AIF clock source changes in MCLK gating (git-fixes).\n- ASoC: xilinx: formatter_pcm: Fix read-modify-write of AUD_CTRL in hw_params (git-fixes).\n- asymmetric_keys: reject trust keys without IDs (git-fixes).\n- ata: libata-scsi: abort multi-sector pass-through commands when multi_count is 0 (git-fixes).\n- ata: libata-scsi: Fix ata_scsi_hotplug() reference in kernel-doc (git-fixes).\n- ata: pata_parport: fix parport attach idr_alloc for (git-fixes).\n- ata: pata_parport: Fix use-after-free in new_device_store (git-fixes).\n- ata: sata_fsl: Fix use-after-free of host_priv on probe() failure (git-fixes).\n- backlight: lm3630a: Cancel delayed work before destroying workqueue (git-fixes).\n- backlight: qcom-wled: Fix NULL pointer dereference in wled_remove() (git-fixes).\n- backlight: qcom-wled: Fix unbalanced OVP IRQ enable at probe (git-fixes).\n- backlight: qcom-wled: Fix WLED3 brightness register stride (git-fixes).\n- Bluetooth: 6lowpan: Drain RCU readers on registration failure (git-fixes).\n- Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file (git-fixes).\n- Bluetooth: 6LoWPAN: Use RCU-safe device list removal (git-fixes).\n- Bluetooth: Add missing newline to bt_dev_{err,warn}_ratelimited() (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btqcomsmd: Convert to platform remove callback returning void (stable-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Keep RCU protection through LTK filtering (git-fixes).\n- Bluetooth: hci_debugfs: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: hci_sync: fix mesh adv timeout units (git-fixes).\n- Bluetooth: hci_sync: Protect IRK identity reads with RCU (git-fixes).\n- Bluetooth: hci_sync: Serialize devcoredump reset during device open (git-fixes).\n- Bluetooth: hci_vhci: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: ISO: Hold the listener during disconnect notification (git-fixes).\n- Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp() (git-fixes).\n- Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm() (git-fixes).\n- Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests (git-fixes).\n- Bluetooth: L2CAP: Reject mode changes on connected channels (git-fixes).\n- Bluetooth: L2CAP: Use default TxWindow for zero socket option (git-fixes).\n- Bluetooth: MGMT: Fix leaking instance on Add Extended Advertising Parameters (git-fixes).\n- Bluetooth: MGMT: Fix pending state of instances added without HCI traffic (git-fixes).\n- Bluetooth: MGMT: Reject quality report requests during unregister (git-fixes).\n- Bluetooth: msft: Lock failed probe cleanup against feature readers (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: selftest: Pin module for selftest debugfs file operations (git-fixes).\n- bus: arm-cci: Drop cci-control-port node reference in __cci_ace_get_port() (git-fixes).\n- bus: arm-cci: Drop CPU node reference in cci_ace_init_ports() (git-fixes).\n- bus: fsl-mc: register the object drivers after misc_class exists (git-fixes).\n- char: scx200_gpio: check cdev_add() return value (git-fixes).\n- checkpatch: skip CamelCase cache for --no-tree without root (git-fixes).\n- cifs: Pass unbyteswapped eof value into SMB2_set_eof() (git-fixes).\n- comedi: comedi_parport: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dmm32at: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dt2811: fix shift-out-of-bounds in IRQ check (git-fixes).\n- comedi: dt2814: validate the IRQ supplied by userspace (git-fixes).\n- comedi: ni_atmio16d: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmmio: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmuio: validate the IRQs supplied by userspace (git-fixes).\n- crypto: amlogic - Fix DMA memory leak in cipher error path (git-fixes).\n- crypto: amlogic - Fix IRQ handler return value and fallthrough logic (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_parse_binary (git-fixes).\n- crypto: atmel - handle authenc requests without plaintext (git-fixes).\n- crypto: atmel-aes - fix AADLENR for standalone GHASH (git-fixes).\n- crypto: atmel-sha - reject initialization without a device (git-fixes).\n- crypto: atmel-tdes - sync output bounce buffer before DMA (git-fixes).\n- crypto: atmel-tdes - zero-initialize device state (git-fixes).\n- crypto: caam - fix double-free in caam_rsa_set_priv_key_form() (git-fixes).\n- crypto: ccp - kill v3 IRQ tasklet during teardown (git-fixes).\n- crypto: ccp - kill v5 IRQ tasklet during teardown (git-fixes).\n- crypto: hisilicon/hpre - fix ECDH destination DMA mapping (git-fixes).\n- crypto: hisilicon/hpre - fix GFP flags for dma_alloc_coherent (git-fixes).\n- crypto: hisilicon/hpre - fix pointer dereference before length check (git-fixes).\n- crypto: hisilicon/hpre - remove dma_free_coherent on NULL req-\u003edst in ECDH (git-fixes).\n- crypto: hisilicon/hpre - return -EOVERFLOW for small ECDH output buffer (git-fixes).\n- crypto: qat - avoid OOB read when stripping RSA leading zeros (git-fixes).\n- crypto: qat - fix active_devs leak on crypto alg registration failure (git-fixes).\n- crypto: qat - fix use of destroyed vf2pf_lock on VF restart (git-fixes).\n- crypto: qat - initialise state_lock on every path in adf_devmgr_add_dev() (git-fixes).\n- crypto: qat - release instance on DH fallback allocation failure (git-fixes).\n- crypto: qat - zero the VF migration state buffer on save (git-fixes).\n- crypto: tcrypt - Avoid reading req-\u003ebase after submission (git-fixes).\n- dmaengine: altera-msgdma: initialize state before requesting IRQ (git-fixes).\n- dmaengine: at_hdmac: Fix use-after-free by proper tasklet cleanup (git-fixes).\n- dmaengine: bestcomm: set bcom_eng to NULL on probe failure (git-fixes).\n- dmaengine: dw-axi-dmac: convert clock handling to clk_bulk API (git-fixes).\n- dmaengine: dw-axi-dmac: Fix AXI burst length encoding (git-fixes).\n- dmaengine: dw-axi-dmac: Fix CH_CFG2 channel priority position (git-fixes).\n- dmaengine: dw-axi-dmac: Fix LLI dump out-of-bounds access (git-fixes).\n- dmaengine: fsl_raid: avoid free_q underflow in free_chan_resources (git-fixes).\n- dmaengine: fsl_raid: don't invoke client callback under desc_lock (git-fixes).\n- dmaengine: fsl_raid: zero CF descriptor pool allocations (git-fixes).\n- dmaengine: img-mdc: Fix runtime PM usage counter leak (git-fixes).\n- dmaengine: ioat: disable relaxed ordering before registering the device (git-fixes).\n- dmaengine: mediatek: hsdma: fix runtime PM leak on init failure (git-fixes).\n- dmaengine: mv_xor: kill tasklet on channel add error path (git-fixes).\n- dmaengine: plx_dma: fix NULL pointer deref in plx_dma_isr() (git-fixes).\n- dmaengine: qcom: bam_dma: Defer IRQ trigger type to device tree (git-fixes).\n- dmaengine: qcom: bam_dma: free interrupt before the clock in error path (git-fixes).\n- dmaengine: sprd: use clk_bulk API to fix clock imbalance (git-fixes).\n- dmaengine: sun6i-dma: Fix use-after-free in error handling paths (git-fixes).\n- dmaengine: xilinx_dma: Fix MCDMA descriptor fields based on DMA direction (git-fixes).\n- Documentation: rs485: Pull uart_get_rs485_mode() from serial_core.c (git-fixes).\n- Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst (git-fixes).\n- driver core: Limit the messages on a refused uevent (git-fixes).\n- drivers/base/node: fix UAF on device_register() failure (git-fixes).\n- drm/amd/display: assign missing trace entry in amdgpu_dm_dc_clocks_state (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amd/display: Fix swap in median3() for DSC rate control (git-fixes).\n- drm/amd/display: fix vready offset assignment in dcn_optc_lock_unlock_state (git-fixes).\n- drm/amd/display: Force GAMCOR for subsampled surfaces with PQ/Gamma22/HLG (git-fixes).\n- drm/amd/display: remove duplicated prev_p_state_change_support assignment (git-fixes).\n- drm/amd/display: take a runtime PM reference only when a CRTC turns on (git-fixes).\n- drm/amd/display: Use kcalloc() instead of kzalloc() (stable-fixes).\n- drm/amd/display: use right type for amdgpu_dc_performance event entries (git-fixes).\n- drm/amd/pm: bound SCLK FCW range entries to the table size (git-fixes).\n- drm/amdgpu/atombios: drop empty function (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang (stable-fixes).\n- drm/amdgpu: Check for multiplication overflow in checkpoint stack (bsc#1276280).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reject ANONONLY userptrs that span multiple VMAs (git-fixes).\n- drm/amdgpu: Remove unused amdgpu_i2c functions (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: rework i2c init and fini (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdgpu: Use dbg level for VBIOS check messages (stable-fixes).\n- drm/amdkfd: evict the queues only once for CRIU PROCESS_INFO (git-fixes).\n- drm/amdkfd: Fix checkpoint-restore on multi-xcc (bsc#1276280).\n- drm/amdkfd: fix doorbell allocation race creating duplicate allocations (git-fixes).\n- drm/amdkfd: validate SRAT subtables before parsing (git-fixes).\n- drm/bridge: analogix_dp: Restore mandatory samsung DP DT properties (git-fixes).\n- drm/exynos/fimd: fix register offset type in fimd_trigger() (git-fixes).\n- drm/imx/lcdc: avoid duplicate clk_per enable (git-fixes).\n- drm/komeda: Fix bits parsing of GLB_CORE_ID (git-fixes).\n- drm/mali-dp: Fix runtime PM leak in malidp_crtc_atomic_enable() (git-fixes).\n- drm/msm/a6xx: Fix secondary rail vote in ARC votes (git-fixes).\n- drm/msm/a6xx: fix use-after-free of OPP in a6xx_pm_resume (git-fixes).\n- drm/msm/dp: don't report link training success after a reinit (git-fixes).\n- drm/msm/dpu: disable the slave encoder before the master (git-fixes).\n- drm/msm/hdmi_phy: Cleanup after msm_hdmi_phy_resource_enable() failure (git-fixes).\n- drm/msm/mdp5: drop cursor pipe for msm8x76 (git-fixes).\n- drm/msm: Properly handle msm_ioremap() without name (git-fixes).\n- drm/nouveau/svm: drain fault handler before freeing svmm (git-fixes).\n- drm/nouveau: cancel the DP IRQ work before freeing the connector (git-fixes).\n- drm/nouveau: disable the fence uevent work instead of just cancelling it (git-fixes).\n- drm/nouveau: don't dereference outp before checking it in nouveau_dp_irq (git-fixes).\n- drm/nouveau: reject zero-size notifier object allocation (git-fixes).\n- drm/omap: dsi: avoid sending bta sync all the time in writes (git-fixes).\n- drm/panel: ebbg-ft8719: Set prepare_prev_first (git-fixes).\n- drm/panfrost: Explicitly enable MMU interrupts at device init (git-fixes).\n- drm/panfrost: Prevent division by 0 (git-fixes).\n- drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence() (git-fixes).\n- drm/tegra: Drop reference on postfence (git-fixes).\n- drm/tegra: Fix syncobj_in wait return value check (git-fixes).\n- drm: of: Fix drm_of_get_data_lanes_count_ep() return value documentation (git-fixes).\n- fbdev: atmel_lcdfb: Prevent FIFO work after removal (git-fixes).\n- fbdev: gxt4500: Release WC setup on probe failure (git-fixes).\n- fbdev: sh_mobile_lcdc: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: smscufx: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: ssd1307fb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use (git-fixes).\n- fbdev: xen-fbfront: check for fb_deferred_io_init() error (git-fixes).\n- firewire: cdev: Fix FW_CDEV_IOC_CREATE_ISO_CONTEXT references in kernel-doc (git-fixes).\n- firmware: cs_dsp: clear dsp-\u003erunning on the cs_dsp_run() error path (git-fixes).\n- firmware: imx: dsp: fix mailbox channel leak on kasprintf failure (git-fixes).\n- fpga: Fix of_fpga_mgr_get() reference in fpga_mgr_lock() docs (git-fixes).\n- gpio: crystalcove: add missing MODULE_ALIAS() (git-fixes).\n- gpio: davinci: Clear interrupt status in every bank on suspend (git-fixes).\n- gpio: mxc: fix both_edges bit operations (git-fixes).\n- gpio: mxc: fix wakeup_pads bit operations (git-fixes).\n- gpio: mxc: use BIT() macro (stable-fixes).\n- gpio: mxc: use lock guards for the generic GPIO chip lock (stable-fixes).\n- gpio: pca953x: Preserve wakeup accounting on parent IRQ failure (git-fixes).\n- HID: alps: unregister DualPoint Stick input device on remove (git-fixes).\n- HID: amd_sfh: Remove unsupported motion-state field from accelerometer report (git-fixes).\n- HID: amd_sfh: Use report type from request node (git-fixes).\n- HID: core: Add reserved item tag for main items (stable-fixes).\n- HID: core: Fix out-of-bounds left shift by 32 in s32ton() (git-fixes).\n- HID: cougar: reject short special-key reports (git-fixes).\n- HID: cp2112: validate response report lengths (git-fixes).\n- HID: elo: reject short touchscreen reports (git-fixes).\n- HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM (stable-fixes).\n- HID: hid-steam: Make client_opened a counter (stable-fixes).\n- HID: logitech-dj: validate unnumbered keyboard reports (git-fixes).\n- HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes (git-fixes).\n- HID: mcp2221: fix OOB write in mcp2221_raw_event() (stable-fixes).\n- HID: mcp2221: validate response report length (git-fixes).\n- HID: picoLCD: check for fb_deferred_io_init() error (git-fixes).\n- HID: pxrc: reject short input reports (git-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: roccat: isku: reject short button reports (git-fixes).\n- HID: roccat: koneplus: reject short button reports (git-fixes).\n- HID: roccat: konepure: reject short button reports (git-fixes).\n- HID: roccat: kovaplus: reject short button reports (git-fixes).\n- HID: roccat: pyra: reject short button reports (git-fixes).\n- HID: roccat: ryos: reject short special reports (git-fixes).\n- HID: roccat: savu: reject short special reports (git-fixes).\n- HID: wacom: fix wacom_intuos_irq NULL pen_input deref (git-fixes).\n- HID: zydacron: validate key report length (git-fixes).\n- hwmon: (coretemp) Refresh the temperature on the first read (git-fixes).\n- hwmon: (corsair-cpro) Make wait_input_report_lock IRQ safe (git-fixes).\n- hwmon: (lm70) Fix rounding of negative temperatures (git-fixes).\n- hwmon: (lm95245) Fix negative temperature conversion (git-fixes).\n- hwmon: (sht3x) Return the consumed count for heater writes (git-fixes).\n- hwrng: amd - report partial reads in non-blocking mode (git-fixes).\n- hwrng: ba431 - fix reported byte count (git-fixes).\n- hwrng: cctrng - Fix runtime PM usage counter leak (git-fixes).\n- hwrng: core - reject unknown RNG names (git-fixes).\n- hwrng: intel - return -ENOMEM when ioremap() fails (git-fixes).\n- hwrng: intel - return -ENOMEM when kmalloc_obj() fails (git-fixes).\n- hwrng: starfive - propagate clock and reset errors (git-fixes).\n- i2c: acpi: Fix adapter reference leak in i2c_acpi_new_device_by_fwnode() (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: designware: queue only one read command for block reads (git-fixes).\n- i2c: mt7621: fix copying uninitialized kernel stack with reduced page_len (git-fixes).\n- i2c: qcom-cci: Fix HALT_ACK reset request being dropped (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- iio: accel: adis16201: fix channel order for buffer mode (git-fixes).\n- iio: accel: kionix-kx022a: Fix IPOL macro name (git-fixes).\n- iio: accel: kxcjk-1013: Disable autosuspend on remove (git-fixes).\n- iio: accel: mma9551: disable autosuspend on remove (git-fixes).\n- iio: accel: mma9553: disable autosuspend on remove (git-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: adc: at91-sama5d2: disable autosuspend on remove (git-fixes).\n- iio: adc: stm32: fix minimum sampling time values (git-fixes).\n- iio: adc: ti-adc128s052: validate SPI match data (git-fixes).\n- iio: core: add accessors 'masklength' (stable-fixes).\n- iio: dac: ad5758: Fix alignment for DMA safety (git-fixes).\n- iio: dac: ad5758: Fix the offset calculation (git-fixes).\n- iio: dac: ad5758: Reject out-of-range raw values (git-fixes).\n- iio: humidity: hts221: report available values via read_avail() (git-fixes).\n- iio: imu: adis16400: Check return value of spi_setup() (git-fixes).\n- iio: light: ltrf216a: Return floating point values (stable-fixes).\n- iio: pressure: dps310: fix CFG_REG bit definitions (git-fixes).\n- iio: temperature: tmp117: fix calibbias cache update on I2C write failure (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: da7280 - fix input device parent assignment (git-fixes).\n- Input: drv2665 - fix input device parent assignment (git-fixes).\n- Input: drv2667 - fix input device parent assignment (git-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: lkkbd - disable pending work before freeing device (stable-fixes).\n- Input: maple_keyb - fix key press detection (git-fixes).\n- Input: maplecontrol - emit EV_SYN report after reporting events (git-fixes).\n- Input: matrix-keymap - reject keycodes above KEY_MAX (git-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: tps6507x-ts - fix input device parent assignment (git-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- kernel-binary.spec.in: Emulate kabi.pl error when suse-kabi-tools is used.\n- kobject: fix out-of-bounds access in kobject_action_type() (git-fixes).\n- kobject: Fix the kobj_set_name reference in kset_register() kernel-doc (git-fixes).\n- KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state (git-fixes).\n- leds: flash: Prevent using uninitialized variable in flash_fault_show() (git-fixes).\n- leds: lm3692x: Fix regulator/gpio leak and wrong enabled state on last write failure (git-fixes).\n- leds: lp8860: Fix device_node leak in lp8860_probe() (git-fixes).\n- leds: pca9532: Check i2c_smbus_read_byte_data() return value (git-fixes).\n- lib/decompress_bunzip2: fix off-by-one in run-length bounds check (git-fixes).\n- lib: decompress_bunzip2: fix integer overflow in run-length decoding (git-fixes).\n- lib: validate in-memory LZ4 chunk length (git-fixes).\n- mac80211: tx: Use info-\u003eflags in ieee80211_tx_h_select_key() (git-fixes).\n- media: adv748x: Fix endpoint reference leaks on probe failure (git-fixes).\n- media: adv7180: Initialize mutex before ancillary clients (git-fixes).\n- media: adv7604: avoid negative array index in log_status when cp_read fails (git-fixes).\n- media: amphion: fix runtime PM imbalance on probe failure (git-fixes).\n- media: amphion: prevent unbind while video instances are open (git-fixes).\n- media: atmel-isi: release unregistered video device on remove (git-fixes).\n- media: au0828: Fix media device leak in au0828_usb_probe() (git-fixes).\n- media: au0828: fix use-after-free in bulk_timeout timer on disconnect (git-fixes).\n- media: au0828: Free URBs when starting DVB streaming fails (git-fixes).\n- media: cx18: Disable PCI device on probe failure (git-fixes).\n- media: cx88: Disable PCI device on MPEG initialization failure (git-fixes).\n- media: cx231xx-audio: drain wq_trigger before audio fini (git-fixes).\n- media: cx231xx: Fix cleanup path on failure (git-fixes).\n- media: cx23885: Fix use-after-free in cx23885_finidev due to race condition (git-fixes).\n- media: cx23885: unregister DVB bus when SP2 CI setup fails (git-fixes).\n- media: em28xx: fix double free in em28xx_alloc_urbs (git-fixes).\n- media: em28xx: reject audio endpoint with zero packet size (git-fixes).\n- media: exynos4-is: Fix a race between s_stream(0) and the interrupt handler (git-fixes).\n- media: go7007: bound EZ-USB I2C transfers to the usb_buf size (git-fixes).\n- media: go7007: unregister the I2C adapter on USB probe failure (git-fixes).\n- media: gspca: use vb2_video_unregister_device() on disconnect (git-fixes).\n- media: hackrf: fix use-after-free in hackrf_alloc_urbs() error path (git-fixes).\n- media: hantro: Disable multicore support (stable-fixes).\n- media: hantro: disable runtime PM before hardware teardown (git-fixes).\n- media: hantro: Harden MPEG-2 control access against NULL (git-fixes).\n- media: i2c: ar0521: remove duplicate media entity cleanup (git-fixes).\n- media: i2c: ov5648: Fix a data race on state-\u003estreaming (git-fixes).\n- media: i2c: ov8856: fix debug message to report actual CSI-2 lane count (git-fixes).\n- media: i2c: tc358743: add missing color-space strings (git-fixes).\n- media: imon: fix use-after-free in display_close via dev_dbg (git-fixes).\n- media: imx-jpeg: cancel timeout worker when streaming stops (git-fixes).\n- media: imx-jpeg: finish the job on device_run() error paths (git-fixes).\n- media: ir-hix5hd2: Ensure rdev is setup before interrupts are enabled (git-fixes).\n- media: ir_toy: Validate the maximum tx carrier (git-fixes).\n- media: m2m-deinterlace: fix default capture field (git-fixes).\n- media: marvell-cam: fix unmet dependency for VIDEO_MMP_CAMERA (git-fixes).\n- media: marvell: manage the MMP camera clock provider (git-fixes).\n- media: mediatek: jpeg: Avoid context access after job finish (git-fixes).\n- media: mediatek: jpeg: retry HW selection after successful wait (git-fixes).\n- media: mediatek: vpu: free IRQ before destroying watchdog workqueue (git-fixes).\n- media: mediatek: vpu: release reserved memory on remove (git-fixes).\n- media: meson-ir-tx: Ensure clock is disabled on unbind (git-fixes).\n- media: meson-ir-tx: Ensure probe error is propagated (git-fixes).\n- media: meson-ir-tx: Prevent divide by zero in meson_irtx_prepare_pulse() (git-fixes).\n- media: meson: vdec: size capture planes from the aligned canvas (git-fixes).\n- media: microchip-csi2dc: fix async notifier leak on probe error path (git-fixes).\n- media: microchip-isc: disable histogram and flush AWB work on teardown (git-fixes).\n- media: microchip-isc: do not touch WB registers when not streaming (git-fixes).\n- media: microchip-isc: fix PM runtime leak in AWB work handler (git-fixes).\n- media: microchip-isc: synchronize the IRQ before disabling clocks on stop (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegdec_worker() (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegenc_worker() (git-fixes).\n- media: platform: mtk-mdp3: Fix device reference leak in mdp_comp_init() (git-fixes).\n- media: pvrusb2: Fix USB parent device leak in class_dev_create() (git-fixes).\n- media: rc: fintek-cir: process a full RX buffer instead of overflowing it (git-fixes).\n- media: rc: mce_kbd: Fix inconsistent locking of keylock (git-fixes).\n- media: redrat3: Ensure all urbs are suspended (git-fixes).\n- media: redrat3: Ensure we don't read beyond the end of the packet (git-fixes).\n- media: redrat3: fix UAF in probe error path leaving rc device registered (git-fixes).\n- media: require two-byte Cypress type 04 records (git-fixes).\n- media: rtl28xxu: fix SDR platform device leak (git-fixes).\n- media: saa7146: Initialize interrupt lock before requesting IRQ (git-fixes).\n- media: streamzap: Add missing rc_unregister_device() (git-fixes).\n- media: stv090x: bound DiSEqC reply length to msg size (git-fixes).\n- media: stv0900: bound DiSEqC reply length to msg size (git-fixes).\n- media: tw68: balance PCI enable on cleanup (git-fixes).\n- media: tw686x: fix V4L2 device lifetime on probe failure (git-fixes).\n- media: uvcvideo: Fix NULL deref on events for uninitialized controls (git-fixes).\n- media: v4l2-ctrls: do nothing if controls == NULL in cluster functions (git-fixes).\n- media: venus: Drop session events without an instance (git-fixes).\n- media: vicodec: fix NULL deref on oversized frame (git-fixes).\n- media: vicodec: fix out-of-bounds write on under-rounded coded dimensions (git-fixes).\n- media: vicodec: make encoder CAPTURE dimensions read-only (git-fixes).\n- media: vicodec: zero-initialize stateful decoder heap buffers (git-fixes).\n- media: vidtv: fix frontend reference leak on unbind (git-fixes).\n- media: vidtv: fix uaf in vidtv_bridge_on_new_pkts_avail (git-fixes).\n- media: vim2m: keep transaction buffer count stable while streaming (git-fixes).\n- media: vivid: round the height down to the vertical subsampling factor (git-fixes).\n- media: vpif_display: Fix i2c adapter reference leak in vpif_probe() (git-fixes).\n- mfd: ab8500: Fix child device leaks on probe failure (git-fixes).\n- mfd: da9150: Balance IRQ wake on teardown (git-fixes).\n- mfd: intel_quark_i2c_gpio: Manage the fixed-rate clock (git-fixes).\n- mfd: tps65217: Check return value when masking interrupt sources (git-fixes).\n- mfd: tps65217: Fix NULL pointer dereference on IRQ init failure (git-fixes).\n- mfd: wcd934x: Fix NULL pointer dereference on IRQ probe deferral (git-fixes).\n- mfd: wcd934x: set DMA mask on parent to silence \"DMA mask not set\" (git-fixes).\n- misc: enclosure: fix UAF on device_register() failure (git-fixes).\n- mm, vmscan: flush tlb before large folio is freed (bsc#1250656).\n- mm: introduce num_pages_contiguous() (bsc#1284243).\n- mtd: amd76xrom: Fix PCI device reference leak in amd76xrom_init_one() (git-fixes).\n- mtd: block: prevent reclaim I/O during request processing (git-fixes).\n- mtd: Call get_wunit() on the master partition (git-fixes).\n- mtd: cfi_cmdset_0002: cap the write-buffer chunk at 256 bytes on an x8 device (git-fixes).\n- mtd: maps: l440gx: Fix double put of the ISA bridge in init_l440gx() (git-fixes).\n- mtd: maps: l440gx: Fix double put of the PM device in init_l440gx() (git-fixes).\n- mtd: maps: pci: balance PCI enable on cleanup (git-fixes).\n- mtd: parsers: qcom: fix offset/size overflow on large partitions (git-fixes).\n- mtd: rawnand: atmel: Fix MCK clock leak in atmel_nand_controller_init() (git-fixes).\n- mtd: rawnand: pl353: fix clk reference leak in pl35x_nfc_setup_interface() (git-fixes).\n- mtd: rawnand: sunxi: reject ECC maximization on small pages (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the SCCR map (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the xSPI Profile 1.0 table (git-fixes).\n- mtd: spi-nor: Unprepare legacy controllers upon RWW wait interruption (git-fixes).\n- mtd: spinand: Fix spinand_manufacturer_ops kernel-doc (git-fixes).\n- net/rds: tcp: don't force RDS_CONN_RESETTING over a concurrent shutdown (git-fixes).\n- net/rds: use clear_bit_unlock() in release_refill() (git-fixes).\n- net: usb: cdc_mbim: don't enable BHs in tx_fixup under netpoll (git-fixes).\n- net: usb: cdc_ncm: don't enable BHs in tx_fixup under netpoll (git-fixes).\n- net: usb: lan78xx: reject invalid EEPROM write requests (git-fixes).\n- net: usb: pegasus: check rx pkt_len against the received length (git-fixes).\n- net: usb: pegasus: do not advance rx_skb-\u003edata on dropped frames (git-fixes).\n- net: usb: r8153_ecm: reject short register reads (git-fixes).\n- net: usb: sierra_net: reject short firmware attribute reads (git-fixes).\n- net: wwan: iosm: validate msg_head before indexing msg_ring (git-fixes).\n- PCI/AER: Fix memory leak in aer_recover_queue() on kfifo buffer overflow (git-fixes).\n- PCI/P2PDMA: Gate the host bridge whitelist warning on verbose (git-fixes).\n- PCI/sysfs: Handle a malformed _DSM result in acpi_attr_is_visible() (git-fixes).\n- PCI/sysfs: Pass the device name length in UTF-16 code units (git-fixes).\n- PCI/sysfs: Stop reporting _DSM failures as -EPERM (git-fixes).\n- PCI: aardvark: Disable PHY on probe failures (git-fixes).\n- PCI: cadence: Preserve all error codes in cdns_plat_pcie_probe() (git-fixes).\n- PCI: Disable MSI for ULi M1575 EHCI controller (git-fixes).\n- PCI: dra7xx: Fix clock enable leak on probe failure (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Pass PF/VF number when BAR programming (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Serialize virtual PCI bus scan (git-fixes).\n- PCI: Fix out-of-bounds MMIO read in nvme_disable_and_flr() (git-fixes).\n- PCI: qcom: Honor IOMMU provider's #iommu-cells in qcom_pcie_config_sid_1_9_0() (git-fixes).\n- PCI: rockchip-host: Do not attempt 5.0 GT/s retraining (git-fixes).\n- PCI: xgene: Use managed clock for PCIe controller (git-fixes).\n- peci: aspeed: Initialize state before requesting IRQ (git-fixes).\n- phy: cadence: Sierra: Do not modify register when getting parent clock (git-fixes).\n- phy: core: Fix race-condition between _of_phy_get() and try_module_get() (git-fixes).\n- phy: HiSilicon: Fix error handling in hi3670_pcie_allclk_ctrl() (git-fixes).\n- phy: hisilicon: hi3670: Fix OF node and device reference leaks (git-fixes).\n- pinctrl: mediatek: mt7629: fix the 2.4 GHz Wi-Fi pin mode array (git-fixes).\n- pinctrl: sprd: free maps on DT map failure (git-fixes).\n- pinctrl: stm32: Fix fwnode reference leak in stm32_gpiolib_register_bank() (git-fixes).\n- platform/chrome: cros_ec_proto: Fix deferred response (git-fixes).\n- platform/olpc: Reserve space for a string terminator (git-fixes).\n- platform/x86/amd/pmc: Fix RTC reference leak in amd_pmc_verify_czn_rtc() (git-fixes).\n- platform/x86/amd: Stop counting intermediate cycles with metrics table (git-fixes).\n- platform/x86/intel-uncore-freq: Continue restoring limits on resume (git-fixes).\n- platform/x86: asus-wmi: validate custom fan curves on enable (git-fixes).\n- platform/x86: gpd pocket fan: Cancel work before releasing GPIOs (git-fixes).\n- platform/x86: hp-wmi: fix heap OOB read and memory corruption in hp_wmi_perform_query() (git-fixes).\n- platform/x86: ibm_rtl: Fix potential OOB read at signature search (git-fixes).\n- platform/x86: intel_telemetry: initialize default trace verbosity (git-fixes).\n- platform/x86: msi-ec: Report valid charge thresholds when unset (git-fixes).\n- power: supply: ab8500: Preserve battery termination current (git-fixes).\n- power: supply: ab8500_btemp: Fix event temperature reporting (git-fixes).\n- power: supply: ab8500_charger: Decode AB8505 USB status (git-fixes).\n- power: supply: ab8500_charger: Fix AC charger re-enable (git-fixes).\n- power: supply: ab8500_charger: Handle detection errors (git-fixes).\n- power: supply: ab8500_charger: Recover inactive AB8505 charger (git-fixes).\n- power: supply: ab8500_charger: Respect AB8505 register layout (git-fixes).\n- power: supply: ab8500_charger: Retry AB8505 USB detection (git-fixes).\n- power: supply: ab8500_charger: Skip absent AB8505 main charger (git-fixes).\n- power: supply: ab8500_fg: Accept status from supplied power (git-fixes).\n- power: supply: ab8500_fg: Avoid reserved AB8505 CCConf bit (git-fixes).\n- power: supply: ab8500_fg: Finalize current measurements (git-fixes).\n- power: supply: ab8500_fg: Report sub-percent charge changes (git-fixes).\n- power: supply: bq2515x: Propagate charge-enable read errors (git-fixes).\n- power: supply: charger-manager: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: generic-adc-battery: fix status with no supplier (git-fixes).\n- power: supply: generic-adc-battery: Propagate charged GPIO errors (git-fixes).\n- power: supply: gpio-charger: Report discharging without input power (git-fixes).\n- power: supply: lp8788-charger: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: lp8788: Use devm_power_supply_register() helper (stable-fixes).\n- power: supply: mp2629: Use the full batt_impedance_compensation name in the ABI document (git-fixes).\n- power: supply: qcom_battmgr: report full batteries (git-fixes).\n- power: supply: qcom_battmgr: report the USB type from USB_ADAP_TYPE (git-fixes).\n- power: supply: sbs-battery: disable polling before supply teardown (git-fixes).\n- pwm: mtk-disp: Fix period readback (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- regulator: ab8500: Fix AB8505 VANA voltage selectors (git-fixes).\n- regulator: ab8500: Handle AB8505 VINTCORE selector 7 (git-fixes).\n- regulator: ab8500: Propagate mode enable read errors (git-fixes).\n- regulator: ab8500: Test dedicated enable bits only (git-fixes).\n- regulator: ab8500: Treat cut 1.0 VAUX3 as fixed (git-fixes).\n- regulator: core: Fix c_rdev reference leak in regulator_resolve_coupling() (git-fixes).\n- regulator: core: Fix coupled regulators reference leak on removal (git-fixes).\n- regulator: core: Fix rdev reference leak in regulator_resolve_supply() (git-fixes).\n- regulator: mp886x: check get_voltage_sel() return value (git-fixes).\n- regulator: mp886x: fix pontential division by zero (git-fixes).\n- regulator: mp886x: fix vsel_mask (git-fixes).\n- regulator: rt6190: Fix runtime PM imbalance in rt6190_out_enable() (git-fixes).\n- Reinstate \"resource: avoid unnecessary lookups in find_next_iomem_res()\" (bsc#1284243).\n- Revert \"mkspec: Exclude rt flavor from kernel-syms dependencies\" (bsc#1244337).\n- Revert \"rpm/mkspec: Fix missing kernel-syms-rt creation\" (bsc#1244337).\n- Revert \"wifi: mac80211: do not use old MBSSID elements\" (git-fixes).\n- rtc: abx80x: fix error check after i2c_smbus_read in read_alarm() (git-fixes).\n- rtc: abx80x: properly handle shared IRQs (git-fixes).\n- rtc: ac100: Assign .num before accessing .hws (git-fixes).\n- rtc: cmos: Disable ACPI RTC event before handling it (git-fixes).\n- rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak (git-fixes).\n- rtc: ds1685: arm the wake-up alarm at power-off only if an alarm is set (git-fixes).\n- rtc: ds1685: do not sleep in the power-off handler (git-fixes).\n- rtc: ftrtc010: fix integer overflow in time calculation (git-fixes).\n- rtc: mpfs: Fix alarm register word order (git-fixes).\n- rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() (git-fixes).\n- rtc: s35390a: Add missing newline to dev_err (git-fixes).\n- rtc: s35390a: Fix alarm not disabling (git-fixes).\n- rtc: spear: initialize IRQ state before requesting alarm IRQ (git-fixes).\n- selftests/alsa: Do not take another control's event as our own (git-fixes).\n- serial: 8250_lpss: do not touch uninitialized line in ehl_serial_exit() (git-fixes).\n- serial: core: shut down initialized port on removal (git-fixes).\n- serial: max310x: don't clobber the TX break bit in set_termios (git-fixes).\n- serial: pmac_zilog: push received data to the port that received it (git-fixes).\n- serial: pmac_zilog: report received breaks (git-fixes).\n- slimbus: messaging: fix leaked PM vote on tid allocation failure (git-fixes).\n- smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- soc/tegra: flowctrl: Release OF node reference on error (git-fixes).\n- soc: fsl: cpm1: tsa: Fix clock leak in tsa_of_parse_tdms() (git-fixes).\n- soc: fsl: dpio: Fix cleanup on IRQ registration failure (git-fixes).\n- soc: fsl: dpio: Free the IRQ before releasing the I/O object (git-fixes).\n- soc: qcom: apr: clean up failed service registrations (git-fixes).\n- soc: ti: k3-ringacc: Correct ring API kernel-doc (git-fixes).\n- soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc (git-fixes).\n- soundwire: intel: initialise quirk_mask before reading it (git-fixes).\n- spi: amd: fix len==0 underflow and FIFO overflow (git-fixes).\n- spi: bcm63xx-hsspi: Disable runtime PM on remove (git-fixes).\n- spi: Fix the return value in spi_new_ancillary_device() kernel-doc (git-fixes).\n- spi: jcore: fix divide-by-zero when speed_hz is zero (git-fixes).\n- spi: mtk-nor: fix runtime PM usage count leak in probe error path (git-fixes).\n- spi: mxic: fix ps_clk leak in runtime resume (git-fixes).\n- spi: npcm-fiu: limit UMA data_size to the 16-byte staging buffer (git-fixes).\n- spi: omap2-mcspi: Remove unbalanced pm_runtime_put_sync() calls (git-fixes).\n- spi: spi-sun4i: sun4i_spi_fill_fifo(): always apply A10 FIFO fill level workaround (git-fixes).\n- spi: spi-sun4i: sun4i_spi_transfer_one(): fix transfers for SUN4I_FIFO_DEPTH (git-fixes).\n- spi: zynq-qspi: fix address buffer corruption and support 4-byte address (git-fixes).\n- staging: iio: adc: ad7816: Fix DMA safety issues in SPI transfers (git-fixes).\n- staging: media: av7110: fix corrupted BER reporting in sp8870 (git-fixes).\n- staging: media: imx: csc-scaler: fix ipu_image_convert_run leak on queue error (git-fixes).\n- staging: rtl8723bs: clean up redundant \u0026 parentheses (stable-fixes).\n- Staging: rtl8723bs: Delete dead code from update_current_network() (stable-fixes).\n- staging: rtl8723bs: fix buffer over-read in rtw_update_protection (git-fixes).\n- staging: rtl8723bs: fix RX buffer OOB write from device-reported length (git-fixes).\n- Staging: rtl8723bs: Remove dead code from _rtw_free_network() (stable-fixes).\n- staging: sm750fb: free cmap on framebuffer release (git-fixes).\n- thermal/drivers/sprd: validate the sensor id from the device tree (git-fixes).\n- thermal: Fix CPU mask truncation in power limit trace event (git-fixes).\n- thermal: intel: int340x: Fix temperature selection around 0 C (git-fixes).\n- thermal: intel: powerclamp: Reject invalid window_size values (git-fixes).\n- thermal: ti-soc-thermal: Fix the return value in ti_bandgap_get_sensor_data() kernel-doc (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- thunderbolt: Do not RPM complete unrelated subtrees on unplug (git-fixes).\n- tools/thermal/tmon: Fix string truncation warning in optarg copy (git-fixes).\n- tpm: fix zero-length read discarding the pending response (git-fixes).\n- tpm: tpm_nsc: fix NULL pointer dereference on init failure (git-fixes).\n- tpm: tpm_nsc: stop using the cleanup callback as dev.release (git-fixes).\n- tty: add break_wait kernel-doc (git-fixes).\n- tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup (stable-fixes).\n- tty: vcc: zero-initialize control packet in vcc_send_ctl() (stable-fixes).\n- usb-storage: alauda: check the return value of alauda_read_map() (git-fixes).\n- usb-storage: alauda: do not do DMA from the stack (git-fixes).\n- usb-storage: alauda: fix out-of-bounds zone index (git-fixes).\n- USB: cdc-acm: fix urb leak on disconnect (git-fixes).\n- usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() (stable-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: dwc3: gadget: Reinitiate stream for all host NoStream behavior (stable-fixes).\n- usb: fotg210: validate endpoint index in ep0 handlers (git-fixes).\n- usb: gadget: composite: avoid warning on aborted delayed status (git-fixes).\n- usb: gadget: dummy_hcd: fix SuperSpeed ep0 maxpacket (git-fixes).\n- usb: gadget: dummy_hcd: prevent unbind via sysfs (git-fixes).\n- usb: gadget: f_fs: Fix Use-After-Free in AIO error path (git-fixes).\n- usb: gadget: f_mass_storage: ignore class requests while inactive (git-fixes).\n- usb: gadget: f_midi: Annotate struct f_midi with __counted_by (stable-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- USB: gadget: ffs: fix mm lifetime handling (stable-fixes).\n- usb: gadget: functionfs: Factorize wait-for-endpoint code (stable-fixes).\n- USB: gadgetfs: do not WARN about excessively large memory allocations (git-fixes).\n- usb: image: microtek: stop SG processing after transfer errors (git-fixes).\n- usb: musb: da8xx: depopulate OF children on probe failure (git-fixes).\n- usb: musb: da8xx: depopulate OF children on remove (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: pci-quirks: Release EHCI device reference (git-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- USB: serial: sierra: fix urb leak on write completion (git-fixes).\n- USB: serial: usb_wwan: fix urb leak on disconnect (git-fixes).\n- usb: typec: ucsi_ccg: Add retry mechanism in ccg_read (git-fixes).\n- USB: usbmon: fix null-ptr-deref in mon_bus_remove() when mon_bus_init() fails (git-fixes).\n- usbnet: fix EVENT_RX_PAUSED race in usbnet_skb_return() (git-fixes).\n- usbnet: fix smp_processor_id() use in preemptible context (git-fixes).\n- vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() (bsc#1284243).\n- vfio/type1: conditional rescheduling while pinning (bsc#1284243).\n- vfio/type1: introduce a new member has_rsvd for struct vfio_dma (bsc#1284243).\n- vfio/type1: optimize vfio_pin_pages_remote() (bsc#1284243).\n- vfio/type1: optimize vfio_unpin_pages_remote() (bsc#1284243).\n- vt: skip screen update for DEC alignment test on backgroup consoles (git-fixes).\n- watchdog: mediatek: Apply the driver's mode to a watchdog left running (git-fixes).\n- wifi: ath6kl: don't take RTNL in del_virtual_intf (git-fixes).\n- wifi: ath9k: delete channel-context timers on deinit (git-fixes).\n- wifi: ath10k: avoid IDR mutation during TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during pending mgmt TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath11k: disable interrupts during firmware crash recovery (git-fixes).\n- wifi: ath11k: fix locking problem in ath11k_dp_rx_tid_del_func() (git-fixes).\n- wifi: ath11k: fix NULL dereference in ahb remove when QMI init incomplete (git-fixes).\n- wifi: ath11k: Fix possible memory leak in ath11k_dp_srng_setup() (git-fixes).\n- wifi: ath11k: fix sporadic WLAN initialization failures (git-fixes).\n- wifi: ath11k: fix unbalanced IRQ enable/disable during suspend/resume (git-fixes).\n- wifi: ath11k: modify null check logic in ath11k_ce_rx_post_pipe() (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: ath11k: unregister PM notifier on QMI init failure path (git-fixes).\n- wifi: ath12k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath12k: fix incorrect TID updation in DP monitor status path (stable-fixes).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (stable-fixes).\n- wifi: ath12k: fix the fetching of combined rssi (git-fixes).\n- wifi: ath12k: Free allocated CE IRQs on request_irq() failure (git-fixes).\n- wifi: b43: don't pass unterminated string to sscanf() (git-fixes).\n- wifi: b43: fix use-after-free in b43_bcma_remove() (git-fixes).\n- wifi: b43legacy: debugfs: NUL terminate string in debugfs (git-fixes).\n- wifi: brcmsmac: Adjust txpwrindex value in nphy_ipa_rxcal_gaintbl_2GHz (git-fixes).\n- wifi: carl9170: NUL terminate string in debugfs (git-fixes).\n- wifi: cfg80211: allow zero HE OBSS PD offsets (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: track SSID regardless of country data (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: iwlwifi: dvm: pair transport op-mode enter/leave (stable-fixes).\n- wifi: iwlwifi: mvm: remove mvm prefix from iwl_mvm_tx_resp* (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: clear fragment cache entry 'is_protected' (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't reset the TXQ scheduling round number (git-fixes).\n- wifi: mac80211: don't send encap offload frames unencrypted (git-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: drop encap offload frames with a tainted key (git-fixes).\n- wifi: mac80211: Fix a race when expiring a mesh path (git-fixes).\n- wifi: mac80211: fix encryption tailroom (git-fixes).\n- wifi: mac80211: fix key selection for encap offload frames (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: fix missing RX bitrate update for mesh forwarding path (stable-fixes).\n- wifi: mac80211: fix swapped fq_overlimit/fq_overmemory in aqm debugfs (git-fixes).\n- wifi: mac80211: Fix the return value in mesh_path_add() kernel-doc (git-fixes).\n- wifi: mac80211: fix unauthorised port check for encap offload (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: init radiotap iter after length checks (git-fixes).\n- wifi: mac80211: kill wake_txqs_tasklet on unregistration (git-fixes).\n- wifi: mac80211: limit injected HT/VHT MCSes (git-fixes).\n- wifi: mac80211: mesh: use hlist_add_head_rcu() (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: refactor populating mesh related fields in sinfo (stable-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: reserve MME tailroom for protected beacons (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mac80211: use link address as TA for non-MLO 4-addr station on MLD AP (git-fixes).\n- wifi: mt76: feed the station RSSI average from the chain signals (git-fixes).\n- wifi: mt76: fix memory leak in USB TX path (git-fixes).\n- wifi: mt76: Fix of_node reference leak in mt76_get_rate_power_limits() (git-fixes).\n- wifi: mt76: fix unlocked wcid check in mt76_tx_status_skb_add() (git-fixes).\n- wifi: mt76: fix wcid-\u003epktid corruption in mt76_wcid_cleanup() (git-fixes).\n- wifi: mt76: mt76x02: validate RX padding before use (git-fixes).\n- wifi: mt76: mt76x02: validate TX-status rate index before mac80211 handoff (git-fixes).\n- wifi: mt76: mt792x: fix UAF in SDIO TX path when out of memory (git-fixes).\n- wifi: mt76: mt7603: don't drop short frames looped back on PS entry (git-fixes).\n- wifi: mt76: mt7615: cancel reset work during unregister (git-fixes).\n- wifi: mt76: mt7615: do not tear down BSS/STA state for monitor vifs (git-fixes).\n- wifi: mt76: mt7615: read MT7663 temperature from the correct offset (git-fixes).\n- wifi: mt76: mt7615: usb: fix source overread in mt7663u_copy (git-fixes).\n- wifi: mt76: mt7615: validate MCU response lengths (git-fixes).\n- wifi: mt76: mt7915: allocate vif wcid in the same range as stations (stable-fixes).\n- wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy (git-fixes).\n- wifi: mt76: mt7915: check default EEPROM firmware size before copying (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: Fix an error handling path in mt7915_add_interface() (git-fixes).\n- wifi: mt76: mt7915: guard firmware memory dump write on disabled memdump (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7915: unregister thermal cooling device on hwmon failure (git-fixes).\n- wifi: mt76: mt7921: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7921: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7921: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7925: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7925: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: honour mac80211's FIF_FCSFAIL instead of hardcoding drop_err (git-fixes).\n- wifi: mt76: mt7925: restore the reset state when fw_pmctrl fails (git-fixes).\n- wifi: mt76: mt7996: fix PLE free page and AC queue register offsets (git-fixes).\n- wifi: mt76: mt7996: validate firmware event lengths before parsing (git-fixes).\n- wifi: mt76: usb: fix source overread in mt76u_copy (git-fixes).\n- wifi: mwifiex: append hotfix number to firmware version string (git-fixes).\n- wifi: p54: validate firmware record lengths (stable-fixes).\n- wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured (git-fixes).\n- wifi: rtw88: debugfs: support multiple adapters debugging (stable-fixes).\n- wifi: rtw88: fix out-of-bounds CAM write when key table is full (git-fixes).\n- wifi: rtw88: sdio: zero the padding added to a TX transfer (git-fixes).\n- wifi: rtw89: 8851b: fix swapped DPK channel/bandwidth backup fields (git-fixes).\n- wifi: rtw89: cap firmware section_num before parsing (git-fixes).\n- wifi: wfx: fix possible device hang during init (git-fixes).\n- wifi: wfx: fix use-after-free of the cooling work on device removal (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wwan: wwan_hwsim: Pin module for debugfs file operations (git-fixes).\n- xhci: dbc: lock the minor IDR on registration failure (git-fixes).\n","status":"published","published":"2026-11-03T19:25:57Z","modified":"2026-11-06T17:23:11.195914364Z","updated_at":"2026-11-06T18:05:03.243497Z"},{"id":"SUSE-SU-2026:5091-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68219: cifs: fix memory leak in smb3_fs_context_parse_param error path (bsc#1255222).\n- CVE-2026-31708: smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path (bsc#1264022).\n- CVE-2026-31709: smb: client: validate the whole DACL before rewriting it in cifsacl (bsc#1264024).\n- CVE-2026-43350: smb: client: require a full NFS mode SID before reading mode bits (bsc#1264985).\n- CVE-2026-46155: smb/client: fix out-of-bounds read in smb2_compound_op() (bsc#1267720).\n- CVE-2026-64370: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (bsc#1273805).\n- CVE-2026-64380: smb: client: harden POSIX SID length parsing (bsc#1273557).\n- CVE-2026-64430: NTB: epf: Avoid calling pci_irq_vector() from hardirq context (bsc#1274257).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-68186: binfmt_misc: set have_execfd only once the interpreter is opened (bsc#1274949).\n- CVE-2026-68436: drm/amd/display: use kvzalloc to allocate struct dc (bsc#1276275).\n- CVE-2026-68447: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size (bsc#1276280).\n- CVE-2026-68460: f2fs: fix potential deadlock in f2fs_balance_fs() (bsc#1276774).\n- CVE-2026-72010: cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed (bsc#1276776).\n- CVE-2026-72073: mmc: vub300: fix use-after-free on probe failure (bsc#1277157).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72111: bpf: Reset register bounds before narrowing retval range in check_mem_access() (bsc#1277389).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72318: cifs: validate DFS referral string offsets (bsc#1275939).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72416: netfilter: nft_compat: ebtables emulation must reject non-bridge targets (bsc#1278041).\n- CVE-2026-72428: bpf: Fix stack slot index in nospec checks (bsc#1278050).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74472: ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev() (bsc#1277785).\n- CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown (bsc#1277903).\n- CVE-2026-74620: net/sched: act_gact, act_police: range check the fallback control action (bsc#1277044).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: net: netfilter: Make ct zone opts configurable for bpf ct helpers (bsc#1277890).\n- CVE-2026-74746: netfilter: flowtable: publish GC-visible tuple last (bsc#1278101).\n- CVE-2026-74748: netfilter: ipset: fix refcount race between list:set GC and swap (bsc#1277578).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80602: perf/x86/amd/lbr: Fix kernel address leakage (bsc#1278123).\n- CVE-2026-80637: netfilter: synproxy: fix unaligned memory access in timestamp adjustment (bsc#1278343).\n- CVE-2026-80717: sctp: validate Adaptation Indication parameter length (bsc#1277836).\n- CVE-2026-80755: selinux: reject a permission value exceeding the class permission count (bsc#1278415).\n- CVE-2026-80757: selinux: reject a class permission count below its inherited common (bsc#1278711).\n- CVE-2026-80808: ext4: stop retrying saturated xattr cache entries (bsc#1279795).\n- CVE-2026-80809: ocfs2: fix missing metadata reservation for large xattrs (bsc#1279606).\n- CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX failure (bsc#1279564).\n- CVE-2026-80879: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write (bsc#1279494).\n- CVE-2026-80881: ocfs2: fix buffer head management in ocfs2_read_blocks() (bsc#1279496).\n- CVE-2026-80978: ip6_gre: fix hardware header length for NBMA tunnels (bsc#1280253).\n- CVE-2026-89491: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() (bsc#1280472).\n- CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler (bsc#1280520).\n- CVE-2026-89495: ocfs2: bound namelen in dlm_migrate_request_handler (bsc#1280569).\n- CVE-2026-89537: SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 (bsc#1280713).\n- CVE-2026-89560: landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation (bsc#1280806).\n- CVE-2026-89595: fsnotify: Fix stale object mask after concurrent mark updates (bsc#1280834).\n- CVE-2026-89608: ecryptfs: pass packet set buffer size to parser (bsc#1280826).\n- CVE-2026-89637: smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed secondary T2 (bsc#1280492).\n- CVE-2026-89649: ceph: bound xattr value length in __build_xattrs() (bsc#1280434).\n- CVE-2026-89654: ceph: fix UAF in check_new_map() on session freed during unlock (bsc#1280415).\n- CVE-2026-89655: ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock (bsc#1280398).\n- CVE-2026-89656: libceph: reject buckets with mismatched CRUSH ids (bsc#1280563).\n- CVE-2026-89657: libceph: validate OSD extent maps before cursor advance (bsc#1280545).\n- CVE-2026-89751: x86/tdx: Fix off-by-one in port I/O handling (bsc#1280822).\n- CVE-2026-89761: apparmor: fix out-of-bounds write when null terminating a label vec (bsc#1280745).\n- CVE-2026-89786: ext4: fix out-of-bounds read in ext4_read_inline_dir() (bsc#1280976).\n- CVE-2026-89787: ext4: check dir entry fits before reading the hash trailer in ext4_search_dir() (bsc#1280977).\n- CVE-2026-90042: ceph: properly decrypt filenames in vmalloc() buffers (bsc#1280948).\n- CVE-2026-90092: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN (bsc#1281384).\n- CVE-2026-90128: vdpa/mlx5: fix wrong list iterated in add_direct_chain error path (bsc#1281577).\n- CVE-2026-90148: NFSv4: Fix incorrect argument passed to nfs4_delete_lease() in nfs4_add_lease() (bsc#1281551).\n- CVE-2026-90227: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (bsc#1281705).\n- CVE-2026-90393: bpf: Fix potential UAF in bpf_netns_link_update_prog (bsc#1282289).\n- CVE-2026-93054: uio: Fix stale info pointer in failed registration path (bsc#1282276).\n- CVE-2026-93228: svcrdma: Reject Write/Reply chunks with segcount 0 (bsc#1282697).\n- CVE-2026-93262: md/raid5-ppl: fix use-after-free in ppl_do_flush() (bsc#1283004).\n- CVE-2026-93795: blk-cgroup: fix leaks and online flag on radix_tree_insert failure (bsc#1283155).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93817: perf: Fix addr_filter_ranges lifetime (bsc#1283017).\n- CVE-2026-97575: media: v4l2-ctrls: validate AV1 tile counts (bsc#1283337).\n- CVE-2026-97605: erofs: preserve LZMA decoders on resize failure (bsc#1283173).\n- CVE-2026-97926: ufs: validate cylinder group metadata before caching it (bsc#1283887).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98086: ALSA: ump: do not touch legacy_rmidi before it exists (bsc#1283785).\n- CVE-2026-98264: ALSA: virtio: reset device before deleting virtqueues (bsc#1284363).\n- CVE-2026-98306: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation (bsc#1284505).\n- CVE-2026-98368: esp: downgrade zerocopy managed frags before mutating skb frags (bsc#1284498).\n- CVE-2026-98374: tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() (bsc#1284740).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-98471: KVM: SEV: Do cache maintenance on the source VM during intra-host migration (bsc#1286240).\n\nThe following non security issues were fixed:\n\n- accel/qaic: reject BO sizes that overflow page count (git-fixes).\n- ACPI: CPPC: Validate the _CPC package header (git-fixes).\n- ACPI: extlog: Validate elog record length before walking sections (git-fixes).\n- ACPI: PCI: pci_link: clear driver_data before free (git-fixes).\n- ACPI: pfr_update: zero-initialize capability query result (git-fixes).\n- ACPI: PM: Drop parent state update from acpi_device_get_power() (git-fixes).\n- ACPI: tables: handle failed initrd override mappings (git-fixes).\n- ACPI: TAD: Rearrange RT data validation checking (stable-fixes).\n- ACPI: video: Fix backlight unregistration ordering (git-fixes).\n- ACPICA: Fix memory leak in acpi_ds_create_field() (git-fixes).\n- ACPICA: Fix PCC OperationRegion command offsets (git-fixes).\n- ALSA: 6fire: take stream_mutex in the Digital Thru control (git-fixes).\n- ALSA: aloop: Keep the timer source alive until card release (git-fixes).\n- ALSA: caiaq: Allow zero-length packet handling for EP1 (git-fixes).\n- ALSA: caiaq: Fix races at MIDI URB and trigger accesses (git-fixes).\n- ALSA: caiaq: Fix the Kore controller key map (git-fixes).\n- ALSA: caiaq: Register card at the final step (git-fixes).\n- ALSA: caiaq: Serialize access to the EP1 command buffer (git-fixes).\n- ALSA: compress: add missing OPEN-state gate to SET_METADATA (git-fixes).\n- ALSA: compress: fix buffer leak on failed SET_PARAMS (git-fixes).\n- ALSA: compress: reject buffer geometry change on gapless next_track (git-fixes).\n- ALSA: control: Fix virtual master creation reference in kernel-doc (git-fixes).\n- ALSA: cs46xx: fix unit mismatch in DSP code area bounds check (git-fixes).\n- ALSA: hda/hdmi: clamp num_cvts against cvt_nids in hdmi_read_pin_conn (git-fixes).\n- ALSA: hda/hdmi: clamp sad_count in ELD proc write handler (git-fixes).\n- ALSA: hda: Add NULL check for the driver pointer at unsol event work (git-fixes).\n- ALSA: hda: Avoid non-operational GPU warning at regular device removal (git-fixes).\n- ALSA: hda: Fix potential UAF for gating jack (git-fixes).\n- ALSA: hda: intel: Cancel delayed work at shutdown, too (git-fixes).\n- ALSA: info: Fix memory leak at card removal (git-fixes).\n- ALSA: jack: Fix kctl free at error in snd_jack_kctl_new() (git-fixes).\n- ALSA: jack: Remove debugfs before freeing unregistered jacks (git-fixes).\n- ALSA: line6: Clear prev_fbuf on capture buffer release (git-fixes).\n- ALSA: line6: Fix potential OOB write in line6_capture_copy() (git-fixes).\n- ALSA: line6: Reject too small max packet sizes (git-fixes).\n- ALSA: line6: Use kzalloc() for PCM buffer allocation (git-fixes).\n- ALSA: pcm: Fix driver_tstamp value reporting (git-fixes).\n- ALSA: pcm: Protect channel-map reads against runtime detach (git-fixes).\n- ALSA: pcm: Protect delay DMA sync against concurrent HW_FREE (git-fixes).\n- ALSA: pcm: Protect delay DMA sync in forward and rewind, too (git-fixes).\n- ALSA: pcm: Protect the unregister notifier traversal (git-fixes).\n- ALSA: pcm: Remove channel-map controls before freeing substreams (git-fixes).\n- ALSA: pcm: Unlink substreams before releasing them (git-fixes).\n- ALSA: rawmidi: Drain input work before freeing the runtime (git-fixes).\n- ALSA: seq: Fix missing direction and ump_group handling in 32bit compat ioctl (git-fixes).\n- ALSA: seq: oss: Skip events until fully initialized (git-fixes).\n- ALSA: ump: Avoid dereference with max_src_size=0 (git-fixes).\n- ALSA: ump: Correct return size of fill_rpn() (git-fixes).\n- ALSA: usb-audio: Use fixed control index for us16x08 mixer elements (git-fixes).\n- ALSA: via82xx: use helper to activate DXS controls (git-fixes).\n- ALSA: vmaster: Protect follower lookup and setup (git-fixes).\n- ASoC: adau17x1: return cache sync errors from resume (git-fixes).\n- ASoC: ak4642: return cache sync errors from resume (git-fixes).\n- ASoC: amd: acp: Fix .close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_sdw_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix acp3x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: renoir: Fix acp_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: vangogh: Fix acp5x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: amd: yc: Fix acp6x_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: arizona-jack: Fix runtime PM imbalance in arizona_start_hpdet_acc_id() (git-fixes).\n- ASoC: atmel-i2s: fix MCK generator error handling (git-fixes).\n- ASoC: atmel-i2s: use optional API for gclk (git-fixes).\n- ASoC: atmel-i2s: use optional API for muxclk (git-fixes).\n- ASoC: atmel: atmel-pcm-pdc: Fix atmel_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: codecs: da732x: Fix definition of ADC2 EQ Overall Volume control (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: use v2.5 Compander1 addresses on v2.5+ (git-fixes).\n- ASoC: codecs: rt5659: propagate GPIO errors (git-fixes).\n- ASoC: codecs: rt5682s: disable jack detection work on shutdown (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: tlv320adc3xxx: Fix definition of AGC Target Level control (git-fixes).\n- ASoC: codecs: wcd9335: Fix SLIM interface device leak in wcd9335_slim_status() (git-fixes).\n- ASoC: codecs: wm5100: Fix definition of EQ3 Band 1 Volume control (git-fixes).\n- ASoC: codecs: wm8510: Fix definition of ADC Inversion Switch control (git-fixes).\n- ASoC: codecs: wm8737: Fix definition of zero cross switches (git-fixes).\n- ASoC: codecs: wm8750: Fix definition of ALC Capture NG Type control (git-fixes).\n- ASoC: codecs: wm8955: Fix definition of Treble Cutoff control (git-fixes).\n- ASoC: codecs: wm8983: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8985: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8994: Fix definition of WM8958 noise gate hold time controls (git-fixes).\n- ASoC: codecs: wm8994: Fix runtime PM leak in wm8994_mic_detect() (git-fixes).\n- ASoC: codecs: wm_hubs: Fix definition of MIXINR to MIXOUTR volume control (git-fixes).\n- ASoC: dwc: Use OF match data again for StarFive JH7110 (git-fixes).\n- ASoC: es8316: return cache sync errors from resume (git-fixes).\n- ASoC: es8326: report resume restore errors (git-fixes).\n- ASoC: fsl_asrc: check the second front-end DMA channel (git-fixes).\n- ASoC: fsl_asrc: use regmap_write_bits to update clock source registers (git-fixes).\n- ASoC: imx-pcm-rpmsg: Fix imx_rpmsg_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: intel: atom: Fix .shutdown() being skipped on rollback (git-fixes).\n- ASoC: Intel: atom: Fix platform device leak on probe failure (git-fixes).\n- ASoC: Intel: avs: Prevent module info underflow (git-fixes).\n- ASoC: Intel: avs: Unprepare a stream when recovery occurs (git-fixes).\n- ASoC: mediatek: common: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: common: Keep codec references until the card is bound (git-fixes).\n- ASoC: mediatek: mt6797: fix wrong unwind order and error code in enable_clock (git-fixes).\n- ASoC: mediatek: mt8183: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8183: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8183: Fix wrong clock cleanup on clk_set_parent() failure (git-fixes).\n- ASoC: mediatek: mt8186: Fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL mux setting error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8186: Fix MCK error handling (git-fixes).\n- ASoC: mediatek: mt8188: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle tuner clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Propagate regmap update errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-pcm: Handle runtime resume errors (git-fixes).\n- ASoC: mediatek: mt8192-mt6359: Fix error handling in MTKAIF calibration (git-fixes).\n- ASoC: mediatek: mt8192: check return values in mt8192_afe_gpio_init() (git-fixes).\n- ASoC: mediatek: mt8192: fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix APLL mux error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix error handling in APLL enable functions (git-fixes).\n- ASoC: mediatek: mt8192: fix MCK clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: Handle regcache_sync() failure in runtime resume (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in I2S DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in TDM DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate mt8192_afe_gpio_request() errors in ADDA DAI (git-fixes).\n- ASoC: mediatek: mt8192: switch to devm_clk_get_optional() (git-fixes).\n- ASoC: mediatek: mt8195: Check paired MEMIF clock enable in FE trigger (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM MCLK error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM probe error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix FE startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix HDMI TX startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix main clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix paired memif clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix register access clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix runtime resume error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix timing system clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix tuner clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Propagate IRQ lookup errors (git-fixes).\n- ASoC: mt6359-accdet: manage private workqueues with devres (git-fixes).\n- ASoC: nau8540: return cache sync errors from resume (git-fixes).\n- ASoC: ops: Fix return value in snd_soc_limit_volume() (git-fixes).\n- ASoC: qcom: q6apm: clear g_apm on driver removal (git-fixes).\n- ASoC: qcom: q6apm: reset the hw pointer with the fragment queue (git-fixes).\n- ASoC: rockchip: rockchip_i2s: Handle runtime PM resume failures in set_fmt (git-fixes).\n- ASoC: rt711-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt711-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: rt712-sdca-dmic: fix drvdata type in the gain controls (git-fixes).\n- ASoC: rt712-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt722-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt1011: return cache sync errors from resume (git-fixes).\n- ASoC: rt1016: return cache sync errors from resume (git-fixes).\n- ASoC: rt1305: return cache sync errors from resume (git-fixes).\n- ASoC: rt1308: return cache sync errors from resume (git-fixes).\n- ASoC: rt5616: return cache sync errors from resume (git-fixes).\n- ASoC: rt5659: return cache sync errors from resume (git-fixes).\n- ASoC: rt5660: return cache sync errors from resume (git-fixes).\n- ASoC: rt5665: return cache sync errors from resume (git-fixes).\n- ASoC: rt5682-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: soc-ac97: Fix error handling in snd_soc_new_ac97_component() (git-fixes).\n- ASoC: soc-component: Fix return type of snd_soc_pcm_component_pointer() (git-fixes).\n- ASoC: soc-topology-test: Check return value of kunit_device_register() (git-fixes).\n- ASoC: SOF: amd: fix amd_sof_acp_remove() teardown ordering (git-fixes).\n- ASoC: SOF: imx: Prevent stack OOB read in DSP panic dump (git-fixes).\n- ASoC: ti: davinci-mcasp: Fix runtime PM imbalance in __davinci_mcasp_set_clkdiv() (git-fixes).\n- ASoC: wcd9335: Fix device reference leak in wcd9335_slim_status() (git-fixes).\n- ASoC: wcd-mbhc-v2: Fix incorrect properties names and typos (git-fixes).\n- ASoC: wm8994: Fix runtime PM imbalance in wm8994_component_probe() (git-fixes).\n- asymmetric_keys: reject trust keys without IDs (git-fixes).\n- ata: libata-scsi: abort multi-sector pass-through commands when multi_count is 0 (git-fixes).\n- ata: libata-scsi: Fix ata_scsi_hotplug() reference in kernel-doc (git-fixes).\n- ata: pata_parport: fix parport attach idr_alloc for (git-fixes).\n- ata: pata_parport: Fix use-after-free in new_device_store (git-fixes).\n- ata: sata_fsl: Fix use-after-free of host_priv on probe() failure (git-fixes).\n- backlight: lm3630a: Cancel delayed work before destroying workqueue (git-fixes).\n- backlight: qcom-wled: Fix NULL pointer dereference in wled_remove() (git-fixes).\n- backlight: qcom-wled: Fix unbalanced OVP IRQ enable at probe (git-fixes).\n- backlight: qcom-wled: Fix WLED3 brightness register stride (git-fixes).\n- Bluetooth: 6lowpan: Drain RCU readers on registration failure (git-fixes).\n- Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file (git-fixes).\n- Bluetooth: 6LoWPAN: Use RCU-safe device list removal (git-fixes).\n- Bluetooth: Add missing newline to bt_dev_{err,warn}_ratelimited() (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btmtk: fix skb double free on ISO padding failure (git-fixes).\n- Bluetooth: btqcomsmd: Convert to platform remove callback returning void (stable-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Keep RCU protection through LTK filtering (git-fixes).\n- Bluetooth: hci_debugfs: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: hci_sync: fix mesh adv timeout units (git-fixes).\n- Bluetooth: hci_sync: Protect IRK identity reads with RCU (git-fixes).\n- Bluetooth: hci_sync: Serialize devcoredump reset during device open (git-fixes).\n- Bluetooth: hci_vhci: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: ISO: Hold the listener during disconnect notification (git-fixes).\n- Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp() (git-fixes).\n- Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm() (git-fixes).\n- Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn (git-fixes).\n- Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests (git-fixes).\n- Bluetooth: L2CAP: Reject mode changes on connected channels (git-fixes).\n- Bluetooth: L2CAP: Use default TxWindow for zero socket option (git-fixes).\n- Bluetooth: MGMT: Fix leaking instance on Add Extended Advertising Parameters (git-fixes).\n- Bluetooth: MGMT: Fix pending state of instances added without HCI traffic (git-fixes).\n- Bluetooth: MGMT: Reject quality report requests during unregister (git-fixes).\n- Bluetooth: msft: Lock failed probe cleanup against feature readers (git-fixes).\n- Bluetooth: MSFT: Serialize handle map cleanup with event processing (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: selftest: Pin module for selftest debugfs file operations (git-fixes).\n- bus: arm-cci: Drop cci-control-port node reference in __cci_ace_get_port() (git-fixes).\n- bus: arm-cci: Drop CPU node reference in cci_ace_init_ports() (git-fixes).\n- bus: fsl-mc: register the object drivers after misc_class exists (git-fixes).\n- char: scx200_gpio: check cdev_add() return value (git-fixes).\n- comedi: comedi_parport: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dmm32at: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dt2811: fix shift-out-of-bounds in IRQ check (git-fixes).\n- comedi: dt2814: validate the IRQ supplied by userspace (git-fixes).\n- comedi: ni_atmio16d: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmmio: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmuio: validate the IRQs supplied by userspace (git-fixes).\n- crypto: amlogic - Fix DMA memory leak in cipher error path (git-fixes).\n- crypto: amlogic - Fix IRQ handler return value and fallthrough logic (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_parse_binary (git-fixes).\n- crypto: atmel - handle authenc requests without plaintext (git-fixes).\n- crypto: atmel-aes - fix AADLENR for standalone GHASH (git-fixes).\n- crypto: atmel-sha - reject initialization without a device (git-fixes).\n- crypto: atmel-tdes - sync output bounce buffer before DMA (git-fixes).\n- crypto: atmel-tdes - zero-initialize device state (git-fixes).\n- crypto: caam - fix double-free in caam_rsa_set_priv_key_form() (git-fixes).\n- crypto: ccp - kill v3 IRQ tasklet during teardown (git-fixes).\n- crypto: ccp - kill v5 IRQ tasklet during teardown (git-fixes).\n- crypto: hisilicon/hpre - fix ECDH destination DMA mapping (git-fixes).\n- crypto: hisilicon/hpre - fix GFP flags for dma_alloc_coherent (git-fixes).\n- crypto: hisilicon/hpre - fix pointer dereference before length check (git-fixes).\n- crypto: hisilicon/hpre - remove dma_free_coherent on NULL req-\u003edst in ECDH (git-fixes).\n- crypto: hisilicon/hpre - return -EOVERFLOW for small ECDH output buffer (git-fixes).\n- crypto: qat - avoid OOB read when stripping RSA leading zeros (git-fixes).\n- crypto: qat - fix active_devs leak on crypto alg registration failure (git-fixes).\n- crypto: qat - fix use of destroyed vf2pf_lock on VF restart (git-fixes).\n- crypto: qat - initialise state_lock on every path in adf_devmgr_add_dev() (git-fixes).\n- crypto: qat - release instance on DH fallback allocation failure (git-fixes).\n- crypto: qat - zero the VF migration state buffer on save (git-fixes).\n- crypto: tcrypt - Avoid reading req-\u003ebase after submission (git-fixes).\n- Documentation: rs485: Pull uart_get_rs485_mode() from serial_core.c (git-fixes).\n- Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst (git-fixes).\n- drivers/base/node: fix UAF on device_register() failure (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- drm/amd/display: assign missing trace entry in amdgpu_dm_dc_clocks_state (git-fixes).\n- drm/amd/display: disable replay when crc source is enabled (stable-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amd/display: fix vready offset assignment in dcn_optc_lock_unlock_state (git-fixes).\n- drm/amd/display: Force GAMCOR for subsampled surfaces with PQ/Gamma22/HLG (git-fixes).\n- drm/amd/display: remove duplicated prev_p_state_change_support assignment (git-fixes).\n- drm/amd/display: Use kcalloc() instead of kzalloc() (stable-fixes).\n- drm/amd/display: use right type for amdgpu_dc_performance event entries (git-fixes).\n- drm/amd/pm: bound SCLK FCW range entries to the table size (git-fixes).\n- drm/amdgpu/atombios: drop empty function (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu: Check for multiplication overflow in checkpoint stack (bsc#1276280).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: Remove unused amdgpu_i2c functions (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: rework i2c init and fini (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdgpu: Update SRIOV Exchange Headers for RAS Telemetry Support (stable-fixes).\n- drm/amdgpu: Use dbg level for VBIOS check messages (stable-fixes).\n- drm/amdkfd: Fix checkpoint-restore on multi-xcc (bsc#1276280).\n- drm/amdkfd: Fix partial migrate issue (stable-fixes).\n- drm/bridge: analogix_dp: Restore mandatory samsung DP DT properties (git-fixes).\n- drm/exynos/fimd: fix register offset type in fimd_trigger() (git-fixes).\n- drm/i915/display: convert I915_STATE_WARN() to struct intel_display (stable-fixes).\n- drm/i915/gmbus: convert to struct intel_display (stable-fixes).\n- drm/i915/vga: Convert VGA code to intel_display (stable-fixes).\n- drm/i915: document range_overflows() and range_end_overflows() macros (stable-fixes).\n- drm/i915: rename range_overflows_end() to range_end_overflows() (stable-fixes).\n- drm/imx/lcdc: avoid duplicate clk_per enable (git-fixes).\n- drm/komeda: Fix bits parsing of GLB_CORE_ID (git-fixes).\n- drm/mali-dp: Fix runtime PM leak in malidp_crtc_atomic_enable() (git-fixes).\n- drm/msm/a6xx: Fix secondary rail vote in ARC votes (git-fixes).\n- drm/msm/a6xx: fix use-after-free of OPP in a6xx_pm_resume (git-fixes).\n- drm/msm/dp: don't report link training success after a reinit (git-fixes).\n- drm/msm/dpu: disable the slave encoder before the master (git-fixes).\n- drm/msm/hdmi_phy: Cleanup after msm_hdmi_phy_resource_enable() failure (git-fixes).\n- drm/msm/mdp5: drop cursor pipe for msm8x76 (git-fixes).\n- drm/msm: Properly handle msm_ioremap() without name (git-fixes).\n- drm/nouveau/svm: drain fault handler before freeing svmm (git-fixes).\n- drm/nouveau: cancel the DP IRQ work before freeing the connector (git-fixes).\n- drm/nouveau: disable the fence uevent work instead of just cancelling it (git-fixes).\n- drm/nouveau: don't dereference outp before checking it in nouveau_dp_irq (git-fixes).\n- drm/nouveau: reject zero-size notifier object allocation (git-fixes).\n- drm/omap: dsi: avoid sending bta sync all the time in writes (git-fixes).\n- drm/panel: ebbg-ft8719: Set prepare_prev_first (git-fixes).\n- drm/panfrost: Explicitly enable MMU interrupts at device init (git-fixes).\n- drm/panfrost: Prevent division by 0 (git-fixes).\n- drm/panthor: Fix TOCTOU race between GROUP_REGISTERED check and erase (git-fixes).\n- drm/panthor: Take reqs_lock in soft_reset for clearing pending_reqs (git-fixes).\n- drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence() (git-fixes).\n- drm/tegra: Drop reference on postfence (git-fixes).\n- drm/tegra: Fix syncobj_in wait return value check (git-fixes).\n- drm/ttm: return an error when kmapping a BO without pages (git-fixes).\n- drm/vc4: Fix firmware reference leak in vc4_drm_bind() (git-fixes).\n- drm/vc4: Use video aperture helpers (stable-fixes).\n- drm/virtio: Add a helper to map and note the dma addrs and lengths (stable-fixes).\n- drm/virtio: Use drm_gem_plane_helper_prepare_fb() (stable-fixes).\n- drm/vmwgfx: Stop using dev_private to store driver data (stable-fixes).\n- drm: of: Fix drm_of_get_data_lanes_count_ep() return value documentation (git-fixes).\n- fbdev: atmel_lcdfb: Prevent FIFO work after removal (git-fixes).\n- fbdev: gxt4500: Release WC setup on probe failure (git-fixes).\n- fbdev: sh_mobile_lcdc: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: smscufx: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: ssd1307fb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use (git-fixes).\n- fbdev: xen-fbfront: check for fb_deferred_io_init() error (git-fixes).\n- firewire: cdev: Fix FW_CDEV_IOC_CREATE_ISO_CONTEXT references in kernel-doc (git-fixes).\n- firmware: cs_dsp: clear dsp-\u003erunning on the cs_dsp_run() error path (git-fixes).\n- firmware: imx: dsp: fix mailbox channel leak on kasprintf failure (git-fixes).\n- fpga: Fix of_fpga_mgr_get() reference in fpga_mgr_lock() docs (git-fixes).\n- gpio: crystalcove: add missing MODULE_ALIAS() (git-fixes).\n- gpio: davinci: Clear interrupt status in every bank on suspend (git-fixes).\n- gpio: pca953x: Preserve wakeup accounting on parent IRQ failure (git-fixes).\n- HID: alps: unregister DualPoint Stick input device on remove (git-fixes).\n- HID: amd_sfh: Remove unsupported motion-state field from accelerometer report (git-fixes).\n- HID: amd_sfh: Use report type from request node (git-fixes).\n- HID: core: Add reserved item tag for main items (stable-fixes).\n- HID: core: Fix out-of-bounds left shift by 32 in s32ton() (git-fixes).\n- HID: cougar: reject short special-key reports (git-fixes).\n- HID: cp2112: validate response report lengths (git-fixes).\n- HID: elo: reject short touchscreen reports (git-fixes).\n- HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM (stable-fixes).\n- HID: hid-steam: Make client_opened a counter (stable-fixes).\n- HID: logitech-dj: validate unnumbered keyboard reports (git-fixes).\n- HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes (git-fixes).\n- HID: mcp2221: fix OOB write in mcp2221_raw_event() (stable-fixes).\n- HID: mcp2221: validate response report length (git-fixes).\n- HID: picoLCD: check for fb_deferred_io_init() error (git-fixes).\n- HID: pxrc: reject short input reports (git-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: roccat: isku: reject short button reports (git-fixes).\n- HID: roccat: koneplus: reject short button reports (git-fixes).\n- HID: roccat: konepure: reject short button reports (git-fixes).\n- HID: roccat: kovaplus: reject short button reports (git-fixes).\n- HID: roccat: pyra: reject short button reports (git-fixes).\n- HID: roccat: ryos: reject short special reports (git-fixes).\n- HID: roccat: savu: reject short special reports (git-fixes).\n- HID: wacom: fix wacom_intuos_irq NULL pen_input deref (git-fixes).\n- HID: zydacron: validate key report length (git-fixes).\n- hostfs: fix dev_t handling (git-fixes).\n- hwmon: (coretemp) Refresh the temperature on the first read (git-fixes).\n- hwmon: (corsair-cpro) Make wait_input_report_lock IRQ safe (git-fixes).\n- hwmon: (lm70) Fix rounding of negative temperatures (git-fixes).\n- hwmon: (lm95245) Fix negative temperature conversion (git-fixes).\n- hwmon: (sht3x) Return the consumed count for heater writes (git-fixes).\n- hwrng: amd - report partial reads in non-blocking mode (git-fixes).\n- hwrng: ba431 - fix reported byte count (git-fixes).\n- hwrng: cctrng - Fix runtime PM usage counter leak (git-fixes).\n- hwrng: core - reject unknown RNG names (git-fixes).\n- hwrng: intel - return -ENOMEM when ioremap() fails (git-fixes).\n- hwrng: intel - return -ENOMEM when kmalloc_obj() fails (git-fixes).\n- hwrng: starfive - propagate clock and reset errors (git-fixes).\n- i2c: acpi: Fix adapter reference leak in i2c_acpi_new_device_by_fwnode() (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: designware: queue only one read command for block reads (git-fixes).\n- i2c: mt7621: fix copying uninitialized kernel stack with reduced page_len (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- iio: accel: adis16201: fix channel order for buffer mode (git-fixes).\n- iio: accel: kionix-kx022a: Fix IPOL macro name (git-fixes).\n- iio: accel: kxcjk-1013: Disable autosuspend on remove (git-fixes).\n- iio: accel: mma9551: disable autosuspend on remove (git-fixes).\n- iio: accel: mma9553: disable autosuspend on remove (git-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: adc: at91-sama5d2: disable autosuspend on remove (git-fixes).\n- iio: adc: stm32: fix minimum sampling time values (git-fixes).\n- iio: adc: ti-adc128s052: validate SPI match data (git-fixes).\n- iio: core: add accessors 'masklength' (stable-fixes).\n- iio: dac: ad5758: Fix alignment for DMA safety (git-fixes).\n- iio: dac: ad5758: Fix the offset calculation (git-fixes).\n- iio: dac: ad5758: Reject out-of-range raw values (git-fixes).\n- iio: humidity: hts221: report available values via read_avail() (git-fixes).\n- iio: imu: adis16400: Check return value of spi_setup() (git-fixes).\n- iio: light: ltrf216a: Return floating point values (stable-fixes).\n- iio: pressure: dps310: fix CFG_REG bit definitions (git-fixes).\n- iio: temperature: tmp117: fix calibbias cache update on I2C write failure (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: da7280 - fix input device parent assignment (git-fixes).\n- Input: drv2665 - fix input device parent assignment (git-fixes).\n- Input: drv2667 - fix input device parent assignment (git-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: lkkbd - disable pending work before freeing device (stable-fixes).\n- Input: maple_keyb - fix key press detection (git-fixes).\n- Input: maplecontrol - emit EV_SYN report after reporting events (git-fixes).\n- Input: matrix-keymap - reject keycodes above KEY_MAX (git-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: tps6507x-ts - fix input device parent assignment (git-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- kobject: fix out-of-bounds access in kobject_action_type() (git-fixes).\n- kobject: Fix the kobj_set_name reference in kset_register() kernel-doc (git-fixes).\n- KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state (git-fixes).\n- landlock: Always allow signals between threads of the same process (git-fixes).\n- landlock: Fix cosmetic change (git-fixes).\n- landlock: Fix non-TCP sockets restriction (git-fixes).\n- landlock: Fix TCP handling of short AF_UNSPEC addresses (git-fixes).\n- landlock: Fix unmarked concurrent access to socket family (git-fixes).\n- leds: flash: Prevent using uninitialized variable in flash_fault_show() (git-fixes).\n- leds: lm3692x: Fix regulator/gpio leak and wrong enabled state on last write failure (git-fixes).\n- leds: lp8860: Fix device_node leak in lp8860_probe() (git-fixes).\n- leds: pca9532: Check i2c_smbus_read_byte_data() return value (git-fixes).\n- mac80211: tx: Use info-\u003eflags in ieee80211_tx_h_select_key() (git-fixes).\n- media: adv748x: Fix endpoint reference leaks on probe failure (git-fixes).\n- media: adv7180: Initialize mutex before ancillary clients (git-fixes).\n- media: adv7604: avoid negative array index in log_status when cp_read fails (git-fixes).\n- media: amphion: fix runtime PM imbalance on probe failure (git-fixes).\n- media: amphion: prevent unbind while video instances are open (git-fixes).\n- media: atmel-isi: release unregistered video device on remove (git-fixes).\n- media: au0828: Fix media device leak in au0828_usb_probe() (git-fixes).\n- media: au0828: fix use-after-free in bulk_timeout timer on disconnect (git-fixes).\n- media: au0828: Free URBs when starting DVB streaming fails (git-fixes).\n- media: cx18: Disable PCI device on probe failure (git-fixes).\n- media: cx88: Disable PCI device on MPEG initialization failure (git-fixes).\n- media: cx231xx-audio: drain wq_trigger before audio fini (git-fixes).\n- media: cx231xx: Fix cleanup path on failure (git-fixes).\n- media: cx23885: Fix use-after-free in cx23885_finidev due to race condition (git-fixes).\n- media: cx23885: unregister DVB bus when SP2 CI setup fails (git-fixes).\n- media: em28xx: fix double free in em28xx_alloc_urbs (git-fixes).\n- media: em28xx: reject audio endpoint with zero packet size (git-fixes).\n- media: exynos4-is: Fix a race between s_stream(0) and the interrupt handler (git-fixes).\n- media: go7007: bound EZ-USB I2C transfers to the usb_buf size (git-fixes).\n- media: go7007: unregister the I2C adapter on USB probe failure (git-fixes).\n- media: gspca: use vb2_video_unregister_device() on disconnect (git-fixes).\n- media: hackrf: fix use-after-free in hackrf_alloc_urbs() error path (git-fixes).\n- media: hantro: Disable multicore support (stable-fixes).\n- media: hantro: disable runtime PM before hardware teardown (git-fixes).\n- media: hantro: Harden MPEG-2 control access against NULL (git-fixes).\n- media: i2c: ar0521: remove duplicate media entity cleanup (git-fixes).\n- media: i2c: ov5648: Fix a data race on state-\u003estreaming (git-fixes).\n- media: i2c: ov8856: fix debug message to report actual CSI-2 lane count (git-fixes).\n- media: i2c: tc358743: add missing color-space strings (git-fixes).\n- media: imon: fix use-after-free in display_close via dev_dbg (git-fixes).\n- media: imx-jpeg: cancel timeout worker when streaming stops (git-fixes).\n- media: imx-jpeg: finish the job on device_run() error paths (git-fixes).\n- media: ir-hix5hd2: Ensure rdev is setup before interrupts are enabled (git-fixes).\n- media: ir_toy: Validate the maximum tx carrier (git-fixes).\n- media: m2m-deinterlace: fix default capture field (git-fixes).\n- media: marvell-cam: fix unmet dependency for VIDEO_MMP_CAMERA (git-fixes).\n- media: marvell: manage the MMP camera clock provider (git-fixes).\n- media: mediatek: jpeg: Avoid context access after job finish (git-fixes).\n- media: mediatek: jpeg: retry HW selection after successful wait (git-fixes).\n- media: mediatek: vpu: free IRQ before destroying watchdog workqueue (git-fixes).\n- media: mediatek: vpu: release reserved memory on remove (git-fixes).\n- media: meson-ir-tx: Ensure clock is disabled on unbind (git-fixes).\n- media: meson-ir-tx: Ensure probe error is propagated (git-fixes).\n- media: meson-ir-tx: Prevent divide by zero in meson_irtx_prepare_pulse() (git-fixes).\n- media: meson: vdec: size capture planes from the aligned canvas (git-fixes).\n- media: microchip-csi2dc: fix async notifier leak on probe error path (git-fixes).\n- media: microchip-isc: disable histogram and flush AWB work on teardown (git-fixes).\n- media: microchip-isc: do not touch WB registers when not streaming (git-fixes).\n- media: microchip-isc: fix PM runtime leak in AWB work handler (git-fixes).\n- media: microchip-isc: synchronize the IRQ before disabling clocks on stop (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegdec_worker() (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegenc_worker() (git-fixes).\n- media: platform: mtk-mdp3: Fix device reference leak in mdp_comp_init() (git-fixes).\n- media: pvrusb2: Fix USB parent device leak in class_dev_create() (git-fixes).\n- media: rc: fintek-cir: process a full RX buffer instead of overflowing it (git-fixes).\n- media: rc: mce_kbd: Fix inconsistent locking of keylock (git-fixes).\n- media: redrat3: Ensure all urbs are suspended (git-fixes).\n- media: redrat3: Ensure we don't read beyond the end of the packet (git-fixes).\n- media: redrat3: fix UAF in probe error path leaving rc device registered (git-fixes).\n- media: require two-byte Cypress type 04 records (git-fixes).\n- media: rtl28xxu: fix SDR platform device leak (git-fixes).\n- media: saa7146: Initialize interrupt lock before requesting IRQ (git-fixes).\n- media: streamzap: Add missing rc_unregister_device() (git-fixes).\n- media: stv090x: bound DiSEqC reply length to msg size (git-fixes).\n- media: stv0900: bound DiSEqC reply length to msg size (git-fixes).\n- media: tw68: balance PCI enable on cleanup (git-fixes).\n- media: tw686x: fix V4L2 device lifetime on probe failure (git-fixes).\n- media: uvcvideo: Fix NULL deref on events for uninitialized controls (git-fixes).\n- media: v4l2-common: Fix P010 format info (git-fixes).\n- media: v4l2-ctrls: do nothing if controls == NULL in cluster functions (git-fixes).\n- media: venus: Drop session events without an instance (git-fixes).\n- media: verisilicon: rockchip: Fix leaks in init (git-fixes).\n- media: vicodec: fix NULL deref on oversized frame (git-fixes).\n- media: vicodec: fix out-of-bounds write on under-rounded coded dimensions (git-fixes).\n- media: vicodec: make encoder CAPTURE dimensions read-only (git-fixes).\n- media: vicodec: zero-initialize stateful decoder heap buffers (git-fixes).\n- media: vidtv: fix frontend reference leak on unbind (git-fixes).\n- media: vidtv: fix uaf in vidtv_bridge_on_new_pkts_avail (git-fixes).\n- media: vim2m: keep transaction buffer count stable while streaming (git-fixes).\n- media: vivid: round the height down to the vertical subsampling factor (git-fixes).\n- media: vpif_display: Fix i2c adapter reference leak in vpif_probe() (git-fixes).\n- mei: vsc-tp: initialize IRQ state before requesting interrupt (git-fixes).\n- mei: vsc: Fix packet CRC computed over pointer size (git-fixes).\n- mfd: ab8500: Fix child device leaks on probe failure (git-fixes).\n- mfd: da9150: Balance IRQ wake on teardown (git-fixes).\n- mfd: intel_quark_i2c_gpio: Manage the fixed-rate clock (git-fixes).\n- mfd: tps65217: Check return value when masking interrupt sources (git-fixes).\n- mfd: tps65217: Fix NULL pointer dereference on IRQ init failure (git-fixes).\n- mfd: wcd934x: Fix NULL pointer dereference on IRQ probe deferral (git-fixes).\n- mfd: wcd934x: set DMA mask on parent to silence 'DMA mask not set' (git-fixes).\n- misc: enclosure: fix UAF on device_register() failure (git-fixes).\n- mm, vmscan: flush tlb before large folio is freed (bsc#1250656).\n- mm: introduce num_pages_contiguous() (bsc#1284243).\n- mtd: amd76xrom: Fix PCI device reference leak in amd76xrom_init_one() (git-fixes).\n- mtd: block: prevent reclaim I/O during request processing (git-fixes).\n- mtd: Call get_wunit() on the master partition (git-fixes).\n- mtd: cfi_cmdset_0002: cap the write-buffer chunk at 256 bytes on an x8 device (git-fixes).\n- mtd: maps: l440gx: Fix double put of the ISA bridge in init_l440gx() (git-fixes).\n- mtd: maps: l440gx: Fix double put of the PM device in init_l440gx() (git-fixes).\n- mtd: maps: pci: balance PCI enable on cleanup (git-fixes).\n- mtd: parsers: qcom: fix offset/size overflow on large partitions (git-fixes).\n- mtd: rawnand: atmel: Fix MCK clock leak in atmel_nand_controller_init() (git-fixes).\n- mtd: rawnand: pl353: fix clk reference leak in pl35x_nfc_setup_interface() (git-fixes).\n- mtd: rawnand: sunxi: reject ECC maximization on small pages (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the SCCR map (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the xSPI Profile 1.0 table (git-fixes).\n- mtd: spi-nor: Unprepare legacy controllers upon RWW wait interruption (git-fixes).\n- mtd: spinand: Fix spinand_manufacturer_ops kernel-doc (git-fixes).\n- net: usb: lan78xx: reject invalid EEPROM write requests (git-fixes).\n- net: usb: r8153_ecm: reject short register reads (git-fixes).\n- net: usb: sierra_net: reject short firmware attribute reads (git-fixes).\n- net: wwan: iosm: validate msg_head before indexing msg_ring (git-fixes).\n- PCI/AER: Fix memory leak in aer_recover_queue() on kfifo buffer overflow (git-fixes).\n- PCI/AER: Fix struct pci_dev reference leak in aer_process_err_devices() (git-fixes).\n- PCI/P2PDMA: Gate the host bridge whitelist warning on verbose (git-fixes).\n- PCI/P2PDMA: Safely terminate ACS redirect lists (git-fixes).\n- PCI/sysfs: Handle a malformed _DSM result in acpi_attr_is_visible() (git-fixes).\n- PCI/sysfs: Pass the device name length in UTF-16 code units (git-fixes).\n- PCI/sysfs: Stop reporting _DSM failures as -EPERM (git-fixes).\n- PCI: aardvark: Disable PHY on probe failures (git-fixes).\n- PCI: cadence: Preserve all error codes in cdns_plat_pcie_probe() (git-fixes).\n- PCI: Disable MSI for ULi M1575 EHCI controller (git-fixes).\n- PCI: dra7xx: Fix clock enable leak on probe failure (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Pass PF/VF number when BAR programming (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Serialize virtual PCI bus scan (git-fixes).\n- PCI: Fix out-of-bounds MMIO read in nvme_disable_and_flr() (git-fixes).\n- PCI: qcom: Honor IOMMU provider's #iommu-cells in qcom_pcie_config_sid_1_9_0() (git-fixes).\n- PCI: rockchip-host: Do not attempt 5.0 GT/s retraining (git-fixes).\n- PCI: xgene: Use managed clock for PCIe controller (git-fixes).\n- peci: aspeed: Initialize state before requesting IRQ (git-fixes).\n- phy: core: Fix race-condition between _of_phy_get() and try_module_get() (git-fixes).\n- pinctrl: mediatek: mt7629: fix the 2.4 GHz Wi-Fi pin mode array (git-fixes).\n- pinctrl: sprd: free maps on DT map failure (git-fixes).\n- pinctrl: stm32: Fix fwnode reference leak in stm32_gpiolib_register_bank() (git-fixes).\n- platform/chrome: cros_ec_proto: Fix deferred response (git-fixes).\n- power: supply: charger-manager: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: lp8788: Use devm_power_supply_register() helper (stable-fixes).\n- pwm: mtk-disp: Fix period readback (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- regulator: ab8500: Fix AB8505 VANA voltage selectors (git-fixes).\n- regulator: ab8500: Handle AB8505 VINTCORE selector 7 (git-fixes).\n- regulator: ab8500: Propagate mode enable read errors (git-fixes).\n- regulator: ab8500: Test dedicated enable bits only (git-fixes).\n- regulator: ab8500: Treat cut 1.0 VAUX3 as fixed (git-fixes).\n- regulator: core: Fix c_rdev reference leak in regulator_resolve_coupling() (git-fixes).\n- regulator: core: Fix coupled regulators reference leak on removal (git-fixes).\n- regulator: core: Fix rdev reference leak in regulator_resolve_supply() (git-fixes).\n- regulator: mp886x: check get_voltage_sel() return value (git-fixes).\n- regulator: mp886x: fix pontential division by zero (git-fixes).\n- regulator: mp886x: fix vsel_mask (git-fixes).\n- regulator: rt6190: Fix runtime PM imbalance in rt6190_out_enable() (git-fixes).\n- Reinstate 'resource: avoid unnecessary lookups in find_next_iomem_res()' (bsc#1284243).\n- Revert 'wifi: mac80211: do not use old MBSSID elements' (git-fixes).\n- rtc: ac100: Assign .num before accessing .hws (git-fixes).\n- rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak (git-fixes).\n- rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() (git-fixes).\n- rtc: spear: initialize IRQ state before requesting alarm IRQ (git-fixes).\n- selftests/alsa: Do not take another control's event as our own (git-fixes).\n- selftests/landlock: Add a new test for setuid() (git-fixes).\n- selftests/landlock: Fix build with non-default pthread linking (git-fixes).\n- selftests/landlock: Fix screwed up pointers in the scoped_signal_test (git-fixes).\n- selftests/landlock: Skip scoped_signal subtest with MSG_OOB if not available (git-fixes).\n- selftests/landlock: Split signal_scoping_threads tests (git-fixes).\n- serial: 8250_lpss: do not touch uninitialized line in ehl_serial_exit() (git-fixes).\n- serial: core: shut down initialized port on removal (git-fixes).\n- serial: max310x: don't clobber the TX break bit in set_termios (git-fixes).\n- serial: pmac_zilog: push received data to the port that received it (git-fixes).\n- serial: pmac_zilog: report received breaks (git-fixes).\n- slimbus: messaging: fix leaked PM vote on tid allocation failure (git-fixes).\n- soc/tegra: flowctrl: Release OF node reference on error (git-fixes).\n- soc: fsl: cpm1: tsa: Fix clock leak in tsa_of_parse_tdms() (git-fixes).\n- soc: fsl: dpio: Fix cleanup on IRQ registration failure (git-fixes).\n- soc: fsl: dpio: Free the IRQ before releasing the I/O object (git-fixes).\n- soc: qcom: apr: clean up failed service registrations (git-fixes).\n- soc: ti: k3-ringacc: Correct ring API kernel-doc (git-fixes).\n- soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc (git-fixes).\n- spi: amd: fix len==0 underflow and FIFO overflow (git-fixes).\n- spi: bcm63xx-hsspi: Disable runtime PM on remove (git-fixes).\n- spi: Fix the return value in spi_new_ancillary_device() kernel-doc (git-fixes).\n- spi: jcore: fix divide-by-zero when speed_hz is zero (git-fixes).\n- spi: mtk-nor: fix runtime PM usage count leak in probe error path (git-fixes).\n- spi: mxic: fix ps_clk leak in runtime resume (git-fixes).\n- spi: npcm-fiu: limit UMA data_size to the 16-byte staging buffer (git-fixes).\n- spi: omap2-mcspi: Remove unbalanced pm_runtime_put_sync() calls (git-fixes).\n- spi: spi-sun4i: sun4i_spi_fill_fifo(): always apply A10 FIFO fill level workaround (git-fixes).\n- spi: spi-sun4i: sun4i_spi_transfer_one(): fix transfers for SUN4I_FIFO_DEPTH (git-fixes).\n- staging: iio: adc: ad7816: Fix DMA safety issues in SPI transfers (git-fixes).\n- staging: media: av7110: fix corrupted BER reporting in sp8870 (git-fixes).\n- staging: media: imx: csc-scaler: fix ipu_image_convert_run leak on queue error (git-fixes).\n- staging: rtl8723bs: clean up redundant \u0026 parentheses (stable-fixes).\n- Staging: rtl8723bs: Delete dead code from update_current_network() (stable-fixes).\n- staging: rtl8723bs: fix buffer over-read in rtw_update_protection (git-fixes).\n- staging: rtl8723bs: fix RX buffer OOB write from device-reported length (git-fixes).\n- Staging: rtl8723bs: Remove dead code from _rtw_free_network() (stable-fixes).\n- staging: sm750fb: free cmap on framebuffer release (git-fixes).\n- thermal/drivers/sprd: validate the sensor id from the device tree (git-fixes).\n- thermal: intel: int340x: Fix temperature selection around 0 C (git-fixes).\n- thermal: intel: powerclamp: Reject invalid window_size values (git-fixes).\n- thermal: ti-soc-thermal: Fix the return value in ti_bandgap_get_sensor_data() kernel-doc (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- thunderbolt: Do not RPM complete unrelated subtrees on unplug (git-fixes).\n- tools/thermal/tmon: Fix string truncation warning in optarg copy (git-fixes).\n- tpm: fix zero-length read discarding the pending response (git-fixes).\n- tpm: tpm_nsc: fix NULL pointer dereference on init failure (git-fixes).\n- tpm: tpm_nsc: stop using the cleanup callback as dev.release (git-fixes).\n- tty: add break_wait kernel-doc (git-fixes).\n- tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup (stable-fixes).\n- tty: vcc: zero-initialize control packet in vcc_send_ctl() (stable-fixes).\n- um: hostfs: avoid issues on inode number reuse by host (git-fixes).\n- usb-storage: alauda: check the return value of alauda_read_map() (git-fixes).\n- usb-storage: alauda: do not do DMA from the stack (git-fixes).\n- usb-storage: alauda: fix out-of-bounds zone index (git-fixes).\n- USB: cdc-acm: fix urb leak on disconnect (git-fixes).\n- usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() (stable-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: dwc3: gadget: Reinitiate stream for all host NoStream behavior (stable-fixes).\n- usb: fotg210: validate endpoint index in ep0 handlers (git-fixes).\n- usb: gadget: composite: avoid warning on aborted delayed status (git-fixes).\n- usb: gadget: dummy_hcd: fix SuperSpeed ep0 maxpacket (git-fixes).\n- usb: gadget: dummy_hcd: prevent unbind via sysfs (git-fixes).\n- usb: gadget: f_fs: Fix Use-After-Free in AIO error path (git-fixes).\n- usb: gadget: f_mass_storage: ignore class requests while inactive (git-fixes).\n- usb: gadget: f_midi: Annotate struct f_midi with __counted_by (stable-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- USB: gadget: ffs: fix mm lifetime handling (stable-fixes).\n- usb: gadget: functionfs: Factorize wait-for-endpoint code (stable-fixes).\n- usb: image: microtek: stop SG processing after transfer errors (git-fixes).\n- usb: musb: da8xx: depopulate OF children on probe failure (git-fixes).\n- usb: musb: da8xx: depopulate OF children on remove (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: pci-quirks: Release EHCI device reference (git-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- USB: serial: sierra: fix urb leak on write completion (git-fixes).\n- USB: serial: usb_wwan: fix urb leak on disconnect (git-fixes).\n- usb: typec: ucsi_ccg: Add retry mechanism in ccg_read (git-fixes).\n- USB: usbmon: fix null-ptr-deref in mon_bus_remove() when mon_bus_init() fails (git-fixes).\n- usbnet: fix smp_processor_id() use in preemptible context (git-fixes).\n- vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() (bsc#1284243).\n- vfio/type1: conditional rescheduling while pinning (bsc#1284243).\n- vfio/type1: introduce a new member has_rsvd for struct vfio_dma (bsc#1284243).\n- vfio/type1: optimize vfio_pin_pages_remote() (bsc#1284243).\n- vfio/type1: optimize vfio_unpin_pages_remote() (bsc#1284243).\n- vt: skip screen update for DEC alignment test on backgroup consoles (git-fixes).\n- watchdog: mediatek: Apply the driver's mode to a watchdog left running (git-fixes).\n- wifi: ath6kl: don't take RTNL in del_virtual_intf (git-fixes).\n- wifi: ath9k: delete channel-context timers on deinit (git-fixes).\n- wifi: ath10k: avoid IDR mutation during TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during pending mgmt TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath11k: disable interrupts during firmware crash recovery (git-fixes).\n- wifi: ath11k: fix locking problem in ath11k_dp_rx_tid_del_func() (git-fixes).\n- wifi: ath11k: fix NULL dereference in ahb remove when QMI init incomplete (git-fixes).\n- wifi: ath11k: Fix possible memory leak in ath11k_dp_srng_setup() (git-fixes).\n- wifi: ath11k: fix sporadic WLAN initialization failures (git-fixes).\n- wifi: ath11k: fix unbalanced IRQ enable/disable during suspend/resume (git-fixes).\n- wifi: ath11k: modify null check logic in ath11k_ce_rx_post_pipe() (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: ath11k: unregister PM notifier on QMI init failure path (git-fixes).\n- wifi: ath12k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath12k: fix incorrect TID updation in DP monitor status path (stable-fixes).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (stable-fixes).\n- wifi: ath12k: fix the fetching of combined rssi (git-fixes).\n- wifi: ath12k: Free allocated CE IRQs on request_irq() failure (git-fixes).\n- wifi: ath12k: Reserve space for a string terminator (git-fixes).\n- wifi: b43: don't pass unterminated string to sscanf() (git-fixes).\n- wifi: b43: fix use-after-free in b43_bcma_remove() (git-fixes).\n- wifi: b43legacy: debugfs: NUL terminate string in debugfs (git-fixes).\n- wifi: brcmsmac: Adjust txpwrindex value in nphy_ipa_rxcal_gaintbl_2GHz (git-fixes).\n- wifi: carl9170: NUL terminate string in debugfs (git-fixes).\n- wifi: cfg80211: allow zero HE OBSS PD offsets (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: track SSID regardless of country data (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: iwlwifi: dvm: pair transport op-mode enter/leave (stable-fixes).\n- wifi: iwlwifi: mvm: remove mvm prefix from iwl_mvm_tx_resp* (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: iwlwifi: simplify nested if checks (stable-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: clear fragment cache entry 'is_protected' (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't reset the TXQ scheduling round number (git-fixes).\n- wifi: mac80211: don't send encap offload frames unencrypted (git-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: drop encap offload frames with a tainted key (git-fixes).\n- wifi: mac80211: Fix a race when expiring a mesh path (git-fixes).\n- wifi: mac80211: fix encryption tailroom (git-fixes).\n- wifi: mac80211: fix key selection for encap offload frames (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: fix missing RX bitrate update for mesh forwarding path (stable-fixes).\n- wifi: mac80211: fix swapped fq_overlimit/fq_overmemory in aqm debugfs (git-fixes).\n- wifi: mac80211: Fix the return value in mesh_path_add() kernel-doc (git-fixes).\n- wifi: mac80211: fix typo in HE MCS check (stable-fixes).\n- wifi: mac80211: fix unauthorised port check for encap offload (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: init radiotap iter after length checks (git-fixes).\n- wifi: mac80211: kill wake_txqs_tasklet on unregistration (git-fixes).\n- wifi: mac80211: limit injected HT/VHT MCSes (git-fixes).\n- wifi: mac80211: log link information in ieee80211_determine_chan_mode (stable-fixes).\n- wifi: mac80211: mesh: use hlist_add_head_rcu() (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: refactor populating mesh related fields in sinfo (stable-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: reserve MME tailroom for protected beacons (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mac80211: use link address as TA for non-MLO 4-addr station on MLD AP (git-fixes).\n- wifi: mt76: feed the station RSSI average from the chain signals (git-fixes).\n- wifi: mt76: fix memory leak in USB TX path (git-fixes).\n- wifi: mt76: Fix of_node reference leak in mt76_get_rate_power_limits() (git-fixes).\n- wifi: mt76: fix unlocked wcid check in mt76_tx_status_skb_add() (git-fixes).\n- wifi: mt76: fix wcid-\u003epktid corruption in mt76_wcid_cleanup() (git-fixes).\n- wifi: mt76: mt76x02: validate RX padding before use (git-fixes).\n- wifi: mt76: mt76x02: validate TX-status rate index before mac80211 handoff (git-fixes).\n- wifi: mt76: mt792x: fix UAF in SDIO TX path when out of memory (git-fixes).\n- wifi: mt76: mt7603: don't drop short frames looped back on PS entry (git-fixes).\n- wifi: mt76: mt7615: cancel reset work during unregister (git-fixes).\n- wifi: mt76: mt7615: do not tear down BSS/STA state for monitor vifs (git-fixes).\n- wifi: mt76: mt7615: read MT7663 temperature from the correct offset (git-fixes).\n- wifi: mt76: mt7615: usb: fix source overread in mt7663u_copy (git-fixes).\n- wifi: mt76: mt7615: validate MCU response lengths (git-fixes).\n- wifi: mt76: mt7915: allocate vif wcid in the same range as stations (stable-fixes).\n- wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy (git-fixes).\n- wifi: mt76: mt7915: check default EEPROM firmware size before copying (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: Fix an error handling path in mt7915_add_interface() (git-fixes).\n- wifi: mt76: mt7915: guard firmware memory dump write on disabled memdump (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7915: unregister thermal cooling device on hwmon failure (git-fixes).\n- wifi: mt76: mt7921: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7921: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7921: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7925: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7925: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: honour mac80211's FIF_FCSFAIL instead of hardcoding drop_err (git-fixes).\n- wifi: mt76: mt7925: restore the reset state when fw_pmctrl fails (git-fixes).\n- wifi: mt76: mt7996: fix PLE free page and AC queue register offsets (git-fixes).\n- wifi: mt76: mt7996: validate firmware event lengths before parsing (git-fixes).\n- wifi: mt76: usb: fix source overread in mt76u_copy (git-fixes).\n- wifi: mwifiex: append hotfix number to firmware version string (git-fixes).\n- wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured (git-fixes).\n- wifi: rtw88: debugfs: support multiple adapters debugging (stable-fixes).\n- wifi: rtw88: fix out-of-bounds CAM write when key table is full (git-fixes).\n- wifi: rtw88: sdio: zero the padding added to a TX transfer (git-fixes).\n- wifi: rtw89: 8851b: fix swapped DPK channel/bandwidth backup fields (git-fixes).\n- wifi: rtw89: cap firmware section_num before parsing (git-fixes).\n- wifi: wfx: fix possible device hang during init (git-fixes).\n- wifi: wfx: fix use-after-free of the cooling work on device removal (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wwan: wwan_hwsim: Pin module for debugfs file operations (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/PCI: Disable enhanced atomics on AMD NBIO 7.7 and 7.11 (git-fixes).\n- xhci: dbc: lock the minor IDR on registration failure (git-fixes).\n","status":"published","published":"2026-11-03T16:27:43Z","modified":"2026-11-04T14:15:08.544785478Z","updated_at":"2026-11-04T14:31:33.296313Z"},{"id":"USN-8886-1","title":"linux-nvidia-tegra vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - Handshake API;\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - OpenRISC architecture;\n  - PowerPC architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Intel NPU Driver;\n  - Android drivers;\n  - Rados block device (RBD) driver;\n  - Bluetooth drivers;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - FireWire subsystem;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Fastrpc Driver;\n  - Amazon Nitro Secure Module driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - NVMEM (Non Volatile Memory) drivers;\n  - Parport drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - System reset/shutdown drivers;\n  - PTP clock framework;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - VME bus staging drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - USB Dual Role (OTG-ready) Controller drivers;\n  - USB Serial drivers;\n  - USB Type-C Port Controller Manager driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - 9P distributed file system;\n  - AFS file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - exFAT file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - SMB network file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Key management;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Glob pattern matching library;\n  - MAC80211 subsystem;\n  - Mellanox drivers;\n  - Networking core;\n  - Network sockets;\n  - IPv6 networking;\n  - Bluetooth subsystem;\n  - Wireless networking;\n  - IPv4 networking;\n  - Netfilter;\n  - Network traffic control;\n  - SCTP protocol;\n  - TCP network protocol;\n  - XFRM subsystem;\n  - RDMA verbs API;\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - Resizable hashtable library;\n  - Memory management;\n  - 6LoWPAN network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - IEEE 802.15.4 subsystem;\n  - Multipath TCP;\n  - Open vSwitch;\n  - Packet sockets;\n  - Phonet protocol;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - SELinux security module;\n  - ALSA framework;\n  - HD-audio driver;\n  - QCOM ASoC drivers;\n  - Simple audio multiplexer codec driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Amlogic Meson SoC drivers;\n  - SOF drivers;\n  - NVIDIA Tegra ASoC drivers;\n  - USB sound devices;\n  - Perf tools;\n  - KVM subsystem;\n(CVE-2025-37807, CVE-2026-23265, CVE-2026-43022, CVE-2026-46321,\nCVE-2026-46322, CVE-2026-52917, CVE-2026-52923, CVE-2026-52927,\nCVE-2026-52929, CVE-2026-52935, CVE-2026-52942, CVE-2026-52943,\nCVE-2026-52947, CVE-2026-52994, CVE-2026-53136, CVE-2026-53137,\nCVE-2026-53138, CVE-2026-53143, CVE-2026-53146, CVE-2026-53147,\nCVE-2026-53149, CVE-2026-53156, CVE-2026-53157, CVE-2026-53160,\nCVE-2026-53161, CVE-2026-53184, CVE-2026-53189, CVE-2026-53194,\nCVE-2026-53195, CVE-2026-53199, CVE-2026-53202, CVE-2026-53205,\nCVE-2026-53209, CVE-2026-53223, CVE-2026-53229, CVE-2026-53253,\nCVE-2026-53255, CVE-2026-53267, CVE-2026-53268, CVE-2026-53272,\nCVE-2026-53329, CVE-2026-53330, CVE-2026-53356, CVE-2026-53362,\nCVE-2026-53365, CVE-2026-53366, CVE-2026-53381, CVE-2026-53383,\nCVE-2026-53387, CVE-2026-53388, CVE-2026-53389, CVE-2026-53390,\nCVE-2026-53391, CVE-2026-53392, CVE-2026-53397, CVE-2026-53400,\nCVE-2026-53401, CVE-2026-53402, CVE-2026-63794, CVE-2026-63802,\nCVE-2026-63803, CVE-2026-63805, CVE-2026-63806, CVE-2026-63809,\nCVE-2026-63812, CVE-2026-63814, CVE-2026-63816, CVE-2026-63817,\nCVE-2026-63819, CVE-2026-63823, CVE-2026-63824, CVE-2026-63827,\nCVE-2026-63833, CVE-2026-63867, CVE-2026-63869, CVE-2026-63870,\nCVE-2026-63875, CVE-2026-63879, CVE-2026-63881, CVE-2026-63884,\nCVE-2026-63889, CVE-2026-63909, CVE-2026-63913, CVE-2026-63920,\nCVE-2026-63925, CVE-2026-63927, CVE-2026-63930, CVE-2026-63942,\nCVE-2026-63954, CVE-2026-63968, CVE-2026-63970, CVE-2026-63971,\nCVE-2026-63985, CVE-2026-64002, CVE-2026-64003, CVE-2026-64004,\nCVE-2026-64005, CVE-2026-64009, CVE-2026-64017, CVE-2026-64023,\nCVE-2026-64026, CVE-2026-64036, CVE-2026-64095, CVE-2026-64123,\nCVE-2026-64188, CVE-2026-64189, CVE-2026-64210, CVE-2026-64222,\nCVE-2026-64239, CVE-2026-64242, CVE-2026-64243, CVE-2026-64245,\nCVE-2026-64246, CVE-2026-64266, CVE-2026-64270, CVE-2026-64271,\nCVE-2026-64272, CVE-2026-64273, CVE-2026-64274, CVE-2026-64276,\nCVE-2026-64277, CVE-2026-64279, CVE-2026-64283, CVE-2026-64286,\nCVE-2026-64287, CVE-2026-64296, CVE-2026-64298, CVE-2026-64299,\nCVE-2026-64304, CVE-2026-64312, CVE-2026-64317, CVE-2026-64318,\nCVE-2026-64322, CVE-2026-64323, CVE-2026-64324, CVE-2026-64333,\nCVE-2026-64368, CVE-2026-64372, CVE-2026-64374, CVE-2026-64375,\nCVE-2026-64378, CVE-2026-64379, CVE-2026-64380, CVE-2026-64388,\nCVE-2026-64389, CVE-2026-64395, CVE-2026-64398, CVE-2026-64401,\nCVE-2026-64402, CVE-2026-64403, CVE-2026-64411, CVE-2026-64412,\nCVE-2026-64413, CVE-2026-64418, CVE-2026-64420, CVE-2026-64422,\nCVE-2026-64423, CVE-2026-64430, CVE-2026-64432, CVE-2026-64435,\nCVE-2026-64436, CVE-2026-64440, CVE-2026-64442, CVE-2026-64443,\nCVE-2026-64444, CVE-2026-64448, CVE-2026-64449, CVE-2026-64452,\nCVE-2026-64456, CVE-2026-64463, CVE-2026-64468, CVE-2026-64469,\nCVE-2026-64481, CVE-2026-64496, CVE-2026-64524, CVE-2026-64532,\nCVE-2026-64533, CVE-2026-64536, CVE-2026-64539, CVE-2026-64540,\nCVE-2026-64543, CVE-2026-64545, CVE-2026-64546, CVE-2026-64547,\nCVE-2026-64550, CVE-2026-64556, CVE-2026-64560, CVE-2026-64563,\nCVE-2026-64567, CVE-2026-64568, CVE-2026-64570, CVE-2026-64574,\nCVE-2026-64576, CVE-2026-64577, CVE-2026-64578, CVE-2026-64580,\nCVE-2026-64581, CVE-2026-64582, CVE-2026-64583, CVE-2026-64584,\nCVE-2026-64585, CVE-2026-64599, CVE-2026-64600, CVE-2026-68091,\nCVE-2026-68096, CVE-2026-68097, CVE-2026-68098, CVE-2026-68100,\nCVE-2026-68104, CVE-2026-68106, CVE-2026-68107, CVE-2026-68108,\nCVE-2026-68116, CVE-2026-68118, CVE-2026-68119, CVE-2026-68121,\nCVE-2026-68125, CVE-2026-68129, CVE-2026-68131, CVE-2026-68140,\nCVE-2026-68141, CVE-2026-68142, CVE-2026-68143, CVE-2026-68145,\nCVE-2026-68148, CVE-2026-68149, CVE-2026-68153, CVE-2026-68155,\nCVE-2026-68157, CVE-2026-68178, CVE-2026-68179, CVE-2026-68189,\nCVE-2026-68192, CVE-2026-68196, CVE-2026-68199, CVE-2026-68202,\nCVE-2026-68204, CVE-2026-68216, CVE-2026-68219, CVE-2026-68222,\nCVE-2026-68236, CVE-2026-68245, CVE-2026-68253, CVE-2026-68255,\nCVE-2026-68258, CVE-2026-68260, CVE-2026-68262, CVE-2026-68263,\nCVE-2026-68266, CVE-2026-68273, CVE-2026-68284, CVE-2026-68287,\nCVE-2026-68290, CVE-2026-68293, CVE-2026-68294, CVE-2026-68297,\nCVE-2026-68299, CVE-2026-68314, CVE-2026-68315, CVE-2026-68320,\nCVE-2026-68322, CVE-2026-68323, CVE-2026-68326, CVE-2026-68329,\nCVE-2026-68335, CVE-2026-68338, CVE-2026-68340, CVE-2026-68348,\nCVE-2026-68352, CVE-2026-68353, CVE-2026-68354, CVE-2026-68370,\nCVE-2026-68371, CVE-2026-68373, CVE-2026-68376, CVE-2026-68377,\nCVE-2026-68383, CVE-2026-68389, CVE-2026-68391, CVE-2026-68392,\nCVE-2026-68397, CVE-2026-68398, CVE-2026-68399, CVE-2026-68400,\nCVE-2026-68401, CVE-2026-68402, CVE-2026-68404, CVE-2026-68408,\nCVE-2026-68409, CVE-2026-68414, CVE-2026-68417, CVE-2026-68419,\nCVE-2026-68425, CVE-2026-68432, CVE-2026-68433, CVE-2026-68442,\nCVE-2026-68445, CVE-2026-68446, CVE-2026-68447, CVE-2026-68451,\nCVE-2026-68452, CVE-2026-68453, CVE-2026-68454, CVE-2026-68466,\nCVE-2026-68467, CVE-2026-68471, CVE-2026-68474, CVE-2026-68479,\nCVE-2026-72005, CVE-2026-72009, CVE-2026-72012, CVE-2026-72019,\nCVE-2026-72021, CVE-2026-72024, CVE-2026-72029, CVE-2026-72035,\nCVE-2026-72036, CVE-2026-72045, CVE-2026-72049, CVE-2026-72051,\nCVE-2026-72052, CVE-2026-72053, CVE-2026-72054, CVE-2026-72055,\nCVE-2026-72057, CVE-2026-72061, CVE-2026-72066, CVE-2026-72067,\nCVE-2026-72072, CVE-2026-72089, CVE-2026-72099, CVE-2026-72102,\nCVE-2026-72105, CVE-2026-72107, CVE-2026-72108, CVE-2026-72109,\nCVE-2026-72110, CVE-2026-72113, CVE-2026-72114, CVE-2026-72115,\nCVE-2026-72116, CVE-2026-72117, CVE-2026-72118, CVE-2026-72119,\nCVE-2026-72120, CVE-2026-72121, CVE-2026-72122, CVE-2026-72123,\nCVE-2026-72133, CVE-2026-72135, CVE-2026-72136, CVE-2026-72144,\nCVE-2026-72146, CVE-2026-72148, CVE-2026-72149, CVE-2026-72157,\nCVE-2026-72160, CVE-2026-72162, CVE-2026-72164, CVE-2026-72165,\nCVE-2026-72170, CVE-2026-72171, CVE-2026-72172, CVE-2026-72175,\nCVE-2026-72181, CVE-2026-72195, CVE-2026-72196, CVE-2026-72197,\nCVE-2026-72213, CVE-2026-72225, CVE-2026-72227, CVE-2026-72231,\nCVE-2026-72232, CVE-2026-72233, CVE-2026-72235, CVE-2026-72242,\nCVE-2026-72243, CVE-2026-72244, CVE-2026-72247, CVE-2026-72250,\nCVE-2026-72252, CVE-2026-72253, CVE-2026-72254, CVE-2026-72261,\nCVE-2026-72262, CVE-2026-72282, CVE-2026-72284, CVE-2026-72297,\nCVE-2026-72298, CVE-2026-72301, CVE-2026-72302, CVE-2026-72304,\nCVE-2026-72310, CVE-2026-72312, CVE-2026-72314, CVE-2026-72330,\nCVE-2026-72334, CVE-2026-72335, CVE-2026-72338, CVE-2026-72340,\nCVE-2026-72342, CVE-2026-72343, CVE-2026-72347, CVE-2026-72350,\nCVE-2026-72352, CVE-2026-72369, CVE-2026-72371, CVE-2026-72373,\nCVE-2026-72374, CVE-2026-72375, CVE-2026-72378, CVE-2026-72382,\nCVE-2026-72389, CVE-2026-72390, CVE-2026-72397, CVE-2026-72400,\nCVE-2026-72404, CVE-2026-72405, CVE-2026-72406, CVE-2026-72409,\nCVE-2026-72410, CVE-2026-72416, CVE-2026-72418, CVE-2026-72419,\nCVE-2026-72420, CVE-2026-72423, CVE-2026-72425, CVE-2026-72427,\nCVE-2026-72435, CVE-2026-72438, CVE-2026-72440, CVE-2026-72444,\nCVE-2026-72449, CVE-2026-72450, CVE-2026-72459, CVE-2026-72460,\nCVE-2026-72464, CVE-2026-72469, CVE-2026-72470, CVE-2026-72476,\nCVE-2026-72478, CVE-2026-72480, CVE-2026-72483, CVE-2026-72485,\nCVE-2026-72492, CVE-2026-72502, CVE-2026-74256, CVE-2026-74257,\nCVE-2026-74258, CVE-2026-74262, CVE-2026-74270, CVE-2026-74281,\nCVE-2026-74282, CVE-2026-74283, CVE-2026-74288, CVE-2026-74289,\nCVE-2026-74292, CVE-2026-74293, CVE-2026-74294, CVE-2026-74295,\nCVE-2026-74296, CVE-2026-74297, CVE-2026-74300, CVE-2026-74312,\nCVE-2026-74313, CVE-2026-74314, CVE-2026-74317, CVE-2026-74321,\nCVE-2026-74330, CVE-2026-74334, CVE-2026-74338, CVE-2026-74340,\nCVE-2026-74341, CVE-2026-74344, CVE-2026-74347, CVE-2026-74349,\nCVE-2026-74356, CVE-2026-74359, CVE-2026-74363, CVE-2026-74365,\nCVE-2026-74374, CVE-2026-74375, CVE-2026-74377, CVE-2026-74378,\nCVE-2026-74380, CVE-2026-74385, CVE-2026-74387, CVE-2026-74388,\nCVE-2026-74390, CVE-2026-74397, CVE-2026-74438, CVE-2026-74443,\nCVE-2026-74444, CVE-2026-74446, CVE-2026-74450, CVE-2026-74453,\nCVE-2026-74454, CVE-2026-74456, CVE-2026-74461, CVE-2026-74465,\nCVE-2026-74467, CVE-2026-74469, CVE-2026-74470, CVE-2026-74471,\nCVE-2026-74479, CVE-2026-74481, CVE-2026-74482, CVE-2026-74485,\nCVE-2026-74488, CVE-2026-74490, CVE-2026-74492, CVE-2026-74496,\nCVE-2026-74497, CVE-2026-74507, CVE-2026-74508, CVE-2026-74509,\nCVE-2026-74510, CVE-2026-74512, CVE-2026-74515, CVE-2026-74516,\nCVE-2026-74518, CVE-2026-74519, CVE-2026-74522, CVE-2026-74523,\nCVE-2026-74527, CVE-2026-74530, CVE-2026-74531, CVE-2026-74533,\nCVE-2026-74534, CVE-2026-74535, CVE-2026-74536, CVE-2026-74537,\nCVE-2026-74540, CVE-2026-74544, CVE-2026-74548, CVE-2026-74549,\nCVE-2026-74550, CVE-2026-74551, CVE-2026-74557, CVE-2026-74563,\nCVE-2026-74564, CVE-2026-74565, CVE-2026-74567, CVE-2026-74572,\nCVE-2026-74574, CVE-2026-74575, CVE-2026-74578, CVE-2026-74579,\nCVE-2026-74580, CVE-2026-74581, CVE-2026-74582, CVE-2026-74583,\nCVE-2026-74584, CVE-2026-74586, CVE-2026-74587, CVE-2026-74588,\nCVE-2026-74589, CVE-2026-74590, CVE-2026-74592, CVE-2026-74594,\nCVE-2026-74595, CVE-2026-74597, CVE-2026-74598, CVE-2026-74601,\nCVE-2026-74603, CVE-2026-74604, CVE-2026-74605, CVE-2026-74606,\nCVE-2026-74607, CVE-2026-74608, CVE-2026-74609, CVE-2026-74610,\nCVE-2026-74611, CVE-2026-74612, CVE-2026-74613, CVE-2026-74614,\nCVE-2026-74615, CVE-2026-74616, CVE-2026-74621, CVE-2026-74624,\nCVE-2026-74625, CVE-2026-74626, CVE-2026-74628, CVE-2026-74630,\nCVE-2026-74631, CVE-2026-74632, CVE-2026-74634, CVE-2026-74635,\nCVE-2026-74637, CVE-2026-74641, CVE-2026-74646, CVE-2026-74647,\nCVE-2026-74648, CVE-2026-74649, CVE-2026-74651, CVE-2026-74656,\nCVE-2026-74660, CVE-2026-74661, CVE-2026-74662, CVE-2026-74663,\nCVE-2026-74666, CVE-2026-74667, CVE-2026-74668, CVE-2026-74669,\nCVE-2026-74670, CVE-2026-74675, CVE-2026-74678, CVE-2026-74684,\nCVE-2026-74687, CVE-2026-74688, CVE-2026-74689, CVE-2026-74690,\nCVE-2026-74691, CVE-2026-74692, CVE-2026-74695, CVE-2026-74696,\nCVE-2026-74697, CVE-2026-74700, CVE-2026-74701, CVE-2026-74704,\nCVE-2026-74705, CVE-2026-74710, CVE-2026-74711, CVE-2026-74713,\nCVE-2026-74714, CVE-2026-74715, CVE-2026-74717, CVE-2026-74720,\nCVE-2026-74723, CVE-2026-74724, CVE-2026-74725, CVE-2026-74726,\nCVE-2026-74730, CVE-2026-74733, CVE-2026-74736, CVE-2026-74737,\nCVE-2026-74739, CVE-2026-74743, CVE-2026-74744, CVE-2026-74746,\nCVE-2026-74747, CVE-2026-74748, CVE-2026-74752, CVE-2026-80521,\nCVE-2026-80526, CVE-2026-80527, CVE-2026-80528, CVE-2026-80536,\nCVE-2026-80540, CVE-2026-80541, CVE-2026-80547, CVE-2026-80548,\nCVE-2026-80549, CVE-2026-80550, CVE-2026-80551, CVE-2026-80552,\nCVE-2026-80553, CVE-2026-80554, CVE-2026-80555, CVE-2026-80556,\nCVE-2026-80557, CVE-2026-80558, CVE-2026-80559, CVE-2026-80560,\nCVE-2026-80561, CVE-2026-80565, CVE-2026-80568, CVE-2026-80569,\nCVE-2026-80570, CVE-2026-80572, CVE-2026-80574, CVE-2026-80576,\nCVE-2026-80578, CVE-2026-80579, CVE-2026-80580, CVE-2026-80583,\nCVE-2026-80584, CVE-2026-80585, CVE-2026-80586, CVE-2026-80587,\nCVE-2026-80589, CVE-2026-80721, CVE-2026-80901, CVE-2026-97509)\n","status":"published","published":"2026-10-06T15:44:31Z","modified":"2026-11-09T12:49:02.511325613Z","updated_at":"2026-11-09T13:27:42.046613Z"},{"id":"USN-8959-1","title":"linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - USB Gadget drivers;\n  - Memory management;\n  - Multiple devices driver;\n  - ARM64 architecture;\n  - EROFS file system;\n  - Networking core;\n  - eXpress Data Path;\n  - ARM32 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - OpenRISC architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Intel NPU Driver;\n  - Speakup Console Speech Driver;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Auxiliary display drivers;\n  - Drivers core;\n  - Micron PCIe SSD driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Hardware random number generator core;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - DIBS (Direct Internal Buffer Sharing) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - FireWire subsystem;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - Google firmware drivers;\n  - Qualcomm firmware drivers;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - HSI subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Mouse) drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - Industry Pack bus drivers;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Multifunction device drivers;\n  - Analog Devices digital potentiometer driver;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - Amazon Nitro Secure Module driver;\n  - SGI GRU 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  - Texas Instruments network drivers;\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  - Operating Performance Points (OPP) driver;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - Mellanox platform drivers;\n  - Microsoft Surface platform drivers;\n  - x86 platform drivers;\n  - MediaTek PM domains;\n  - Power sequencing drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - MPAM driver;\n  - RPMSG subsystem;\n  - Real Time Clock drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - USB DSL drivers;\n  - Cypress C67X00 USB driver;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - Intel La Jolla Cove Adapter USB driver;\n  - Intel USBIO USB I/O expander driver;\n  - USB Serial drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\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  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - AFS file system;\n  - BFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - debug file system;\n  - eCrypt file system;\n  - EFI Variable file system;\n  - exFAT 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  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Overlay file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UBI file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Tracing infrastructure;\n  - Kernel futex primitives;\n  - Memory Management;\n  - VLANs driver;\n  - IPv4 networking;\n  - io_uring subsystem;\n  - KProbes tracing;\n  - KVM subsystem;\n  - Live Update Orchestrator (LUO);\n  - Netfilter;\n  - Perf events;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Networking subsytem;\n  - Slab allocator;\n  - Sun RPC protocol;\n  - Vector I/O iterator library;\n  - Virtio network driver;\n  - Network traffic control;\n  - IPv6 networking;\n  - Bluetooth subsystem;\n  - IEEE 802.15.4 subsystem;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - NFC subsystem;\n  - SCTP protocol;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - Audit subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - DMA mapping infrastructure;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - IRQ subsystem;\n  - KCOV code coverage framework;\n  - Locking primitives;\n  - Kernel module support;\n  - Namespaces infrastructure;\n  - Kernel command line parsing driver;\n  - PID allocator;\n  - printk logging mechanism;\n  - System reboot mechanism;\n  - Timer subsystem;\n  - Workqueue subsystem;\n  - Kernel build system;\n  - Heterogeneous memory management;\n  - UCS-2 string library;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Devlink API;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IFE protocol;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - L2TP protocol;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netlink;\n  - Open vSwitch;\n  - Packet sockets;\n  - Phonet protocol;\n  - PSP security protocol;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Linux Security Modules (LSM) Framework;\n  - Key management;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - Generic sound devices;\n  - HD-audio driver;\n  - ESS ES18xx ALSA driver;\n  - ICE1712/ICE1724 (Envy24) ALSA driver;\n  - Digigram PCXHR ALSA driver;\n  - AMD SoC Alsa drivers;\n  - Cirrus Logic audio codecs;\n  - QCOM ASoC drivers;\n  - Realtek audio codecs;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - Rockchip ASoC drivers;\n  - SoundWire (SDCA) ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Spreadtrum ASoC drivers;\n  - STI ASoC drivers;\n  - Xilinx ASoC drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n(CVE-2026-100070, CVE-2026-100071, CVE-2026-100072, CVE-2026-100073,\nCVE-2026-100074, CVE-2026-100075, CVE-2026-100076, CVE-2026-100077,\nCVE-2026-100078, CVE-2026-100079, CVE-2026-68451, CVE-2026-68452,\nCVE-2026-68453, CVE-2026-74440, CVE-2026-74441, CVE-2026-74442,\nCVE-2026-74443, CVE-2026-74444, CVE-2026-74445, CVE-2026-74446,\nCVE-2026-74447, CVE-2026-74448, CVE-2026-74449, CVE-2026-74450,\nCVE-2026-74451, CVE-2026-74452, CVE-2026-74453, CVE-2026-74454,\nCVE-2026-74455, CVE-2026-74456, CVE-2026-74457, CVE-2026-74458,\nCVE-2026-74459, CVE-2026-74460, CVE-2026-74461, CVE-2026-74462,\nCVE-2026-74463, CVE-2026-74464, CVE-2026-74465, CVE-2026-74466,\nCVE-2026-74467, CVE-2026-74468, CVE-2026-74469, CVE-2026-74470,\nCVE-2026-74471, CVE-2026-74472, CVE-2026-74473, CVE-2026-74474,\nCVE-2026-74475, CVE-2026-74476, CVE-2026-74477, CVE-2026-74478,\nCVE-2026-74479, CVE-2026-74480, CVE-2026-74481, CVE-2026-74482,\nCVE-2026-74483, CVE-2026-74484, CVE-2026-74485, CVE-2026-74486,\nCVE-2026-74487, CVE-2026-74488, CVE-2026-74490, CVE-2026-74491,\nCVE-2026-74492, CVE-2026-74493, CVE-2026-74494, CVE-2026-74495,\nCVE-2026-74496, CVE-2026-74497, CVE-2026-74498, CVE-2026-74499,\nCVE-2026-74500, CVE-2026-74501, CVE-2026-74502, CVE-2026-74503,\nCVE-2026-74504, CVE-2026-74505, CVE-2026-74506, CVE-2026-74507,\nCVE-2026-74508, CVE-2026-74509, CVE-2026-74510, CVE-2026-74512,\nCVE-2026-74513, CVE-2026-74514, CVE-2026-74515, CVE-2026-74516,\nCVE-2026-74517, CVE-2026-74518, CVE-2026-74519, CVE-2026-74520,\nCVE-2026-74521, CVE-2026-74522, CVE-2026-74523, CVE-2026-74524,\nCVE-2026-74525, CVE-2026-74526, CVE-2026-74528, CVE-2026-74529,\nCVE-2026-74530, CVE-2026-74531, CVE-2026-74532, CVE-2026-74533,\nCVE-2026-74534, CVE-2026-74535, CVE-2026-74536, CVE-2026-74537,\nCVE-2026-74538, CVE-2026-74539, CVE-2026-74540, CVE-2026-74541,\nCVE-2026-74542, CVE-2026-74543, CVE-2026-74544, CVE-2026-74545,\nCVE-2026-74546, CVE-2026-74547, CVE-2026-74548, CVE-2026-74549,\nCVE-2026-74550, CVE-2026-74551, CVE-2026-74552, CVE-2026-74553,\nCVE-2026-74554, CVE-2026-74555, CVE-2026-74556, CVE-2026-74557,\nCVE-2026-74558, CVE-2026-74559, CVE-2026-74560, CVE-2026-74561,\nCVE-2026-74562, CVE-2026-74563, CVE-2026-74564, CVE-2026-74565,\nCVE-2026-74566, CVE-2026-74567, CVE-2026-74569, CVE-2026-74571,\nCVE-2026-74572, CVE-2026-74573, CVE-2026-74574, CVE-2026-74575,\nCVE-2026-74576, CVE-2026-74577, CVE-2026-74579, CVE-2026-74580,\nCVE-2026-74581, CVE-2026-74582, CVE-2026-74583, CVE-2026-74585,\nCVE-2026-74586, CVE-2026-74587, CVE-2026-74588, CVE-2026-74589,\nCVE-2026-74590, CVE-2026-74591, CVE-2026-74592, CVE-2026-74593,\nCVE-2026-74594, CVE-2026-74595, CVE-2026-74596, CVE-2026-74597,\nCVE-2026-74598, CVE-2026-74599, CVE-2026-74600, CVE-2026-74601,\nCVE-2026-74602, CVE-2026-74603, CVE-2026-74604, CVE-2026-74605,\nCVE-2026-74606, CVE-2026-74607, CVE-2026-74608, CVE-2026-74609,\nCVE-2026-74610, CVE-2026-74611, CVE-2026-74612, CVE-2026-74613,\nCVE-2026-74614, CVE-2026-74615, CVE-2026-74616, CVE-2026-74617,\nCVE-2026-74618, CVE-2026-74619, CVE-2026-74620, CVE-2026-74621,\nCVE-2026-74622, CVE-2026-74623, CVE-2026-74624, CVE-2026-74625,\nCVE-2026-74626, CVE-2026-74627, CVE-2026-74628, CVE-2026-74629,\nCVE-2026-74630, CVE-2026-74631, CVE-2026-74632, CVE-2026-74633,\nCVE-2026-74634, CVE-2026-74635, CVE-2026-74636, CVE-2026-74637,\nCVE-2026-74638, CVE-2026-74639, CVE-2026-74640, CVE-2026-74641,\nCVE-2026-74643, CVE-2026-74644, CVE-2026-74645, CVE-2026-74646,\nCVE-2026-74647, CVE-2026-74648, CVE-2026-74649, CVE-2026-74650,\nCVE-2026-74651, CVE-2026-74652, CVE-2026-74653, CVE-2026-74654,\nCVE-2026-74655, CVE-2026-74656, CVE-2026-74657, CVE-2026-74658,\nCVE-2026-74659, CVE-2026-74660, CVE-2026-74661, CVE-2026-74662,\nCVE-2026-74663, CVE-2026-74664, CVE-2026-74665, CVE-2026-74666,\nCVE-2026-74667, CVE-2026-74668, CVE-2026-74669, CVE-2026-74670,\nCVE-2026-74671, CVE-2026-74672, CVE-2026-74673, CVE-2026-74674,\nCVE-2026-74675, CVE-2026-74676, CVE-2026-74677, CVE-2026-74678,\nCVE-2026-74679, CVE-2026-74680, CVE-2026-74681, CVE-2026-74682,\nCVE-2026-74683, CVE-2026-74684, CVE-2026-74685, CVE-2026-74686,\nCVE-2026-74687, CVE-2026-74688, CVE-2026-74689, CVE-2026-74690,\nCVE-2026-74691, CVE-2026-74692, CVE-2026-74693, CVE-2026-74694,\nCVE-2026-74695, CVE-2026-74696, CVE-2026-74697, CVE-2026-74698,\nCVE-2026-74699, CVE-2026-74700, CVE-2026-74701, CVE-2026-74702,\nCVE-2026-74703, CVE-2026-74704, CVE-2026-74705, CVE-2026-74706,\nCVE-2026-74707, CVE-2026-74708, CVE-2026-74709, CVE-2026-74710,\nCVE-2026-74711, CVE-2026-74712, CVE-2026-74713, CVE-2026-74714,\nCVE-2026-74715, CVE-2026-74716, CVE-2026-74717, CVE-2026-74718,\nCVE-2026-74719, CVE-2026-74720, CVE-2026-74721, CVE-2026-74722,\nCVE-2026-74723, CVE-2026-74724, CVE-2026-74725, CVE-2026-74726,\nCVE-2026-74727, CVE-2026-74728, CVE-2026-74729, CVE-2026-74730,\nCVE-2026-74733, CVE-2026-74734, CVE-2026-74735, CVE-2026-74736,\nCVE-2026-74737, CVE-2026-74738, CVE-2026-74739, CVE-2026-74740,\nCVE-2026-74741, CVE-2026-74742, CVE-2026-74743, CVE-2026-74744,\nCVE-2026-74745, CVE-2026-74746, CVE-2026-74747, CVE-2026-74748,\nCVE-2026-74750, CVE-2026-74752, CVE-2026-74753, CVE-2026-74754,\nCVE-2026-80519, CVE-2026-80520, CVE-2026-80521, CVE-2026-80522,\nCVE-2026-80523, CVE-2026-80524, CVE-2026-80525, CVE-2026-80526,\nCVE-2026-80527, CVE-2026-80528, CVE-2026-80529, CVE-2026-80530,\nCVE-2026-80531, CVE-2026-80532, CVE-2026-80533, CVE-2026-80534,\nCVE-2026-80535, CVE-2026-80536, CVE-2026-80537, CVE-2026-80538,\nCVE-2026-80539, CVE-2026-80540, CVE-2026-80541, CVE-2026-80542,\nCVE-2026-80547, CVE-2026-80548, CVE-2026-80549, CVE-2026-80550,\nCVE-2026-80551, CVE-2026-80552, CVE-2026-80553, CVE-2026-80554,\nCVE-2026-80555, CVE-2026-80556, CVE-2026-80557, CVE-2026-80558,\nCVE-2026-80559, CVE-2026-80560, CVE-2026-80561, CVE-2026-80562,\nCVE-2026-80563, CVE-2026-80564, CVE-2026-80565, CVE-2026-80566,\nCVE-2026-80567, CVE-2026-80568, CVE-2026-80569, CVE-2026-80570,\nCVE-2026-80571, CVE-2026-80572, CVE-2026-80573, CVE-2026-80574,\nCVE-2026-80575, CVE-2026-80576, CVE-2026-80577, CVE-2026-80578,\nCVE-2026-80579, CVE-2026-80580, CVE-2026-80581, CVE-2026-80582,\nCVE-2026-80583, CVE-2026-80584, CVE-2026-80585, CVE-2026-80586,\nCVE-2026-80587, CVE-2026-80588, CVE-2026-80589, CVE-2026-80590,\nCVE-2026-80678, CVE-2026-80679, CVE-2026-80680, CVE-2026-80681,\nCVE-2026-80683, CVE-2026-80684, CVE-2026-80685, CVE-2026-80686,\nCVE-2026-80687, CVE-2026-80688, CVE-2026-80689, CVE-2026-80690,\nCVE-2026-80691, CVE-2026-80692, CVE-2026-80693, CVE-2026-80694,\nCVE-2026-80695, CVE-2026-80696, CVE-2026-80697, CVE-2026-80698,\nCVE-2026-80699, CVE-2026-80700, CVE-2026-80701, CVE-2026-80702,\nCVE-2026-80703, CVE-2026-80704, CVE-2026-80705, CVE-2026-80706,\nCVE-2026-80707, CVE-2026-80708, CVE-2026-80709, CVE-2026-80710,\nCVE-2026-80711, CVE-2026-80712, CVE-2026-80713, CVE-2026-80714,\nCVE-2026-80715, CVE-2026-80716, CVE-2026-80717, CVE-2026-80718,\nCVE-2026-80720, CVE-2026-80721, CVE-2026-80722, CVE-2026-80723,\nCVE-2026-80724, CVE-2026-80727, CVE-2026-80729, CVE-2026-80730,\nCVE-2026-80731, CVE-2026-80732, CVE-2026-80733, CVE-2026-80734,\nCVE-2026-80735, CVE-2026-80736, CVE-2026-80737, CVE-2026-80738,\nCVE-2026-80739, CVE-2026-80740, CVE-2026-80741, CVE-2026-80742,\nCVE-2026-80743, CVE-2026-80744, CVE-2026-80745, CVE-2026-80747,\nCVE-2026-80748, CVE-2026-80749, CVE-2026-80750, CVE-2026-80751,\nCVE-2026-80752, CVE-2026-80753, CVE-2026-80754, CVE-2026-80755,\nCVE-2026-80756, CVE-2026-80757, CVE-2026-80758, CVE-2026-80759,\nCVE-2026-80760, CVE-2026-80761, CVE-2026-80762, CVE-2026-80763,\nCVE-2026-80764, CVE-2026-80765, CVE-2026-80766, CVE-2026-80767,\nCVE-2026-80768, CVE-2026-80769, CVE-2026-80770, CVE-2026-80771,\nCVE-2026-80772, CVE-2026-80774, CVE-2026-80775, CVE-2026-80776,\nCVE-2026-80777, CVE-2026-80778, CVE-2026-80779, CVE-2026-80780,\nCVE-2026-80781, CVE-2026-80782, CVE-2026-80783, CVE-2026-80784,\nCVE-2026-80785, CVE-2026-80786, CVE-2026-80787, CVE-2026-80788,\nCVE-2026-80789, CVE-2026-80790, CVE-2026-80791, CVE-2026-80792,\nCVE-2026-80793, CVE-2026-80794, CVE-2026-80795, CVE-2026-80796,\nCVE-2026-80797, CVE-2026-80798, CVE-2026-80799, CVE-2026-80800,\nCVE-2026-80801, CVE-2026-80802, CVE-2026-80803, CVE-2026-80804,\nCVE-2026-80805, CVE-2026-80806, CVE-2026-80807, CVE-2026-80808,\nCVE-2026-80809, CVE-2026-80810, CVE-2026-80811, CVE-2026-80812,\nCVE-2026-80813, CVE-2026-80814, CVE-2026-80815, CVE-2026-80816,\nCVE-2026-80817, CVE-2026-80818, CVE-2026-80819, CVE-2026-80820,\nCVE-2026-80821, CVE-2026-80822, CVE-2026-80823, CVE-2026-80824,\nCVE-2026-80825, CVE-2026-80826, CVE-2026-80827, CVE-2026-80828,\nCVE-2026-80829, CVE-2026-80830, CVE-2026-80831, CVE-2026-80832,\nCVE-2026-80833, CVE-2026-80834, CVE-2026-80835, CVE-2026-80836,\nCVE-2026-80837, CVE-2026-80838, CVE-2026-80839, CVE-2026-80840,\nCVE-2026-80841, CVE-2026-80842, CVE-2026-80843, CVE-2026-80844,\nCVE-2026-80845, CVE-2026-80846, CVE-2026-80847, CVE-2026-80848,\nCVE-2026-80849, CVE-2026-80850, CVE-2026-80851, CVE-2026-80852,\nCVE-2026-80854, CVE-2026-80855, CVE-2026-80856, CVE-2026-80857,\nCVE-2026-80858, CVE-2026-80859, CVE-2026-80860, CVE-2026-80861,\nCVE-2026-80862, CVE-2026-80863, CVE-2026-80864, CVE-2026-80887,\nCVE-2026-80888, CVE-2026-80889, CVE-2026-80890, CVE-2026-80891,\nCVE-2026-80892, CVE-2026-80893, CVE-2026-80894, CVE-2026-80895,\nCVE-2026-80896, CVE-2026-80897, CVE-2026-80898, CVE-2026-80899,\nCVE-2026-80900, CVE-2026-80901, CVE-2026-80902, CVE-2026-80903,\nCVE-2026-80904, CVE-2026-80905, CVE-2026-80906, CVE-2026-80907,\nCVE-2026-80908, CVE-2026-80909, CVE-2026-80910, CVE-2026-80911,\nCVE-2026-80912, CVE-2026-80913, CVE-2026-80914, CVE-2026-80915,\nCVE-2026-80916, CVE-2026-80917, CVE-2026-80918, CVE-2026-80920,\nCVE-2026-80921, CVE-2026-80922, CVE-2026-80923, CVE-2026-80924,\nCVE-2026-80925, CVE-2026-80926, CVE-2026-80927, CVE-2026-80928,\nCVE-2026-80929, CVE-2026-80930, CVE-2026-80931, CVE-2026-80932,\nCVE-2026-80933, CVE-2026-80934, CVE-2026-80935, CVE-2026-80936,\nCVE-2026-80937, CVE-2026-80938, CVE-2026-80939, CVE-2026-80940,\nCVE-2026-80941, CVE-2026-80942, CVE-2026-80943, CVE-2026-80944,\nCVE-2026-80945, CVE-2026-80946, CVE-2026-80947, CVE-2026-80948,\nCVE-2026-80949, CVE-2026-80950, CVE-2026-80951, CVE-2026-80952,\nCVE-2026-80953, CVE-2026-80954, CVE-2026-80955, CVE-2026-80956,\nCVE-2026-80957, CVE-2026-80958, CVE-2026-80959, CVE-2026-80960,\nCVE-2026-80961, CVE-2026-80962, CVE-2026-80963, CVE-2026-80964,\nCVE-2026-80965, CVE-2026-80966, CVE-2026-80967, CVE-2026-80968,\nCVE-2026-80969, CVE-2026-80970, CVE-2026-80971, CVE-2026-80972,\nCVE-2026-80973, CVE-2026-80974, CVE-2026-80975, CVE-2026-80976,\nCVE-2026-80977, CVE-2026-80978, CVE-2026-80979, CVE-2026-80980,\nCVE-2026-80981, CVE-2026-80982, CVE-2026-80983, CVE-2026-80984,\nCVE-2026-80985, CVE-2026-80986, CVE-2026-80987, CVE-2026-80988,\nCVE-2026-80989, CVE-2026-80990, CVE-2026-80991, CVE-2026-80992,\nCVE-2026-80993, CVE-2026-80994, CVE-2026-80996, CVE-2026-80997,\nCVE-2026-80999, CVE-2026-81000, CVE-2026-81001, CVE-2026-81002,\nCVE-2026-81003, CVE-2026-81004, CVE-2026-81005, CVE-2026-81006,\nCVE-2026-81007, CVE-2026-81008, CVE-2026-81009, CVE-2026-81010,\nCVE-2026-81011, CVE-2026-81012, CVE-2026-81013, CVE-2026-81014,\nCVE-2026-81015, CVE-2026-81016, CVE-2026-81017, CVE-2026-81018,\nCVE-2026-89437, CVE-2026-89438, CVE-2026-89439, CVE-2026-89440,\nCVE-2026-89441, CVE-2026-89442, CVE-2026-89443, CVE-2026-89444,\nCVE-2026-89445, CVE-2026-89446, CVE-2026-89447, CVE-2026-89448,\nCVE-2026-89449, CVE-2026-89450, CVE-2026-89451, CVE-2026-89452,\nCVE-2026-89453, CVE-2026-89454, CVE-2026-89455, CVE-2026-89456,\nCVE-2026-89457, CVE-2026-89458, CVE-2026-89460, CVE-2026-89461,\nCVE-2026-89462, CVE-2026-89463, CVE-2026-89464, CVE-2026-89465,\nCVE-2026-89466, CVE-2026-89467, CVE-2026-89468, CVE-2026-89469,\nCVE-2026-89470, CVE-2026-89471, CVE-2026-89472, CVE-2026-89473,\nCVE-2026-89474, CVE-2026-89475, CVE-2026-89476, CVE-2026-89477,\nCVE-2026-89478, CVE-2026-89479, CVE-2026-89480, CVE-2026-89481,\nCVE-2026-89482, CVE-2026-89483, CVE-2026-89484, CVE-2026-89485,\nCVE-2026-89486, CVE-2026-89487, CVE-2026-89488, CVE-2026-89489,\nCVE-2026-89490, CVE-2026-89491, CVE-2026-89492, CVE-2026-89493,\nCVE-2026-89494, CVE-2026-89495, CVE-2026-89496, CVE-2026-89497,\nCVE-2026-89498, CVE-2026-89500, CVE-2026-89501, CVE-2026-89502,\nCVE-2026-89503, CVE-2026-89504, CVE-2026-89506, CVE-2026-89507,\nCVE-2026-89508, CVE-2026-89509, CVE-2026-89510, CVE-2026-89511,\nCVE-2026-89512, CVE-2026-89513, CVE-2026-89514, CVE-2026-89515,\nCVE-2026-89520, CVE-2026-89521, CVE-2026-89522, CVE-2026-89523,\nCVE-2026-89524, CVE-2026-89525, CVE-2026-89526, CVE-2026-89527,\nCVE-2026-89528, CVE-2026-89529, CVE-2026-89530, CVE-2026-89531,\nCVE-2026-89532, CVE-2026-89533, CVE-2026-89534, CVE-2026-89535,\nCVE-2026-89536, CVE-2026-89537, CVE-2026-89538, CVE-2026-89539,\nCVE-2026-89540, CVE-2026-89541, CVE-2026-89542, CVE-2026-89543,\nCVE-2026-89544, CVE-2026-89545, CVE-2026-89546, CVE-2026-89547,\nCVE-2026-89548, CVE-2026-89549, CVE-2026-89550, CVE-2026-89551,\nCVE-2026-89552, CVE-2026-89553, CVE-2026-89554, CVE-2026-89555,\nCVE-2026-89556, CVE-2026-89557, CVE-2026-89558, CVE-2026-89559,\nCVE-2026-89560, CVE-2026-89561, CVE-2026-89562, CVE-2026-89563,\nCVE-2026-89564, CVE-2026-89565, CVE-2026-89566, CVE-2026-89567,\nCVE-2026-89569, CVE-2026-89570, CVE-2026-89571, CVE-2026-89572,\nCVE-2026-89573, CVE-2026-89574, CVE-2026-89575, CVE-2026-89576,\nCVE-2026-89577, CVE-2026-89578, CVE-2026-89579, CVE-2026-89580,\nCVE-2026-89581, CVE-2026-89582, CVE-2026-89583, CVE-2026-89584,\nCVE-2026-89585, CVE-2026-89586, CVE-2026-89587, CVE-2026-89588,\nCVE-2026-89589, CVE-2026-89590, CVE-2026-89591, CVE-2026-89592,\nCVE-2026-89593, CVE-2026-89594, CVE-2026-89595, CVE-2026-89596,\nCVE-2026-89597, CVE-2026-89598, CVE-2026-89599, CVE-2026-89600,\nCVE-2026-89601, CVE-2026-89602, CVE-2026-89604, CVE-2026-89605,\nCVE-2026-89606, CVE-2026-89607, CVE-2026-89608, CVE-2026-89609,\nCVE-2026-89615, CVE-2026-89616, CVE-2026-89617, CVE-2026-89618,\nCVE-2026-89619, CVE-2026-89620, CVE-2026-89621, CVE-2026-89622,\nCVE-2026-89623, CVE-2026-89624, CVE-2026-89625, CVE-2026-89626,\nCVE-2026-89627, CVE-2026-89628, CVE-2026-89629, CVE-2026-89630,\nCVE-2026-89631, CVE-2026-89632, CVE-2026-89633, CVE-2026-89634,\nCVE-2026-89636, CVE-2026-89637, CVE-2026-89638, CVE-2026-89640,\nCVE-2026-89641, CVE-2026-89642, CVE-2026-89643, CVE-2026-89644,\nCVE-2026-89645, CVE-2026-89646, CVE-2026-89647, CVE-2026-89648,\nCVE-2026-89649, CVE-2026-89650, CVE-2026-89651, CVE-2026-89652,\nCVE-2026-89653, CVE-2026-89654, CVE-2026-89655, CVE-2026-89656,\nCVE-2026-89657, CVE-2026-89658, CVE-2026-89659, CVE-2026-89660,\nCVE-2026-89661, CVE-2026-89662, CVE-2026-89663, CVE-2026-89664,\nCVE-2026-89665, CVE-2026-89666, CVE-2026-89667, CVE-2026-89668,\nCVE-2026-89669, CVE-2026-89670, CVE-2026-89671, CVE-2026-89672,\nCVE-2026-89673, CVE-2026-89674, CVE-2026-89675, CVE-2026-89676,\nCVE-2026-89677, CVE-2026-89678, CVE-2026-89679, CVE-2026-89680,\nCVE-2026-89682, CVE-2026-89683, CVE-2026-89684, CVE-2026-89685,\nCVE-2026-89686, CVE-2026-89687, CVE-2026-89688, CVE-2026-89689,\nCVE-2026-89690, CVE-2026-89691, CVE-2026-89692, CVE-2026-89693,\nCVE-2026-89694, CVE-2026-89695, CVE-2026-89696, CVE-2026-89697,\nCVE-2026-89698, CVE-2026-89699, CVE-2026-89700, CVE-2026-89701,\nCVE-2026-89702, CVE-2026-89703, CVE-2026-89704, CVE-2026-89705,\nCVE-2026-89706, CVE-2026-89707, CVE-2026-89708, CVE-2026-89709,\nCVE-2026-89710, CVE-2026-89711, CVE-2026-89712, CVE-2026-89713,\nCVE-2026-89714, CVE-2026-89715, CVE-2026-89716, CVE-2026-89717,\nCVE-2026-89718, CVE-2026-89719, CVE-2026-89720, CVE-2026-89721,\nCVE-2026-89722, CVE-2026-89723, CVE-2026-89724, CVE-2026-89725,\nCVE-2026-89726, CVE-2026-89727, CVE-2026-89728, CVE-2026-89729,\nCVE-2026-89730, CVE-2026-89731, CVE-2026-89732, CVE-2026-89733,\nCVE-2026-89734, CVE-2026-89735, CVE-2026-89736, CVE-2026-89737,\nCVE-2026-89738, CVE-2026-89739, CVE-2026-89740, CVE-2026-89741,\nCVE-2026-89742, CVE-2026-89743, CVE-2026-89744, CVE-2026-89745,\nCVE-2026-89746, CVE-2026-89747, CVE-2026-89749, CVE-2026-89750,\nCVE-2026-89751, CVE-2026-89752, CVE-2026-89753, CVE-2026-89754,\nCVE-2026-89755, CVE-2026-89756, CVE-2026-89757, CVE-2026-89758,\nCVE-2026-89759, CVE-2026-89761, CVE-2026-89762, CVE-2026-89763,\nCVE-2026-89765, CVE-2026-89766, CVE-2026-89767, CVE-2026-89768,\nCVE-2026-89769, CVE-2026-89771, CVE-2026-89775, CVE-2026-89776,\nCVE-2026-89777, CVE-2026-89778, CVE-2026-89779, CVE-2026-89780,\nCVE-2026-89781, CVE-2026-89782, CVE-2026-89783, CVE-2026-89784,\nCVE-2026-89785, CVE-2026-89786, CVE-2026-89787, CVE-2026-89788,\nCVE-2026-89789, CVE-2026-89790, CVE-2026-89791, CVE-2026-89792,\nCVE-2026-89793, CVE-2026-89794, CVE-2026-89795, CVE-2026-89796,\nCVE-2026-89797, CVE-2026-89798, CVE-2026-89799, CVE-2026-89800,\nCVE-2026-89801, CVE-2026-89802, CVE-2026-89803, CVE-2026-89804,\nCVE-2026-89806, CVE-2026-89807, CVE-2026-89808, CVE-2026-89809,\nCVE-2026-89810, CVE-2026-89811, CVE-2026-89812, CVE-2026-89813,\nCVE-2026-89814, CVE-2026-89815, CVE-2026-89816, CVE-2026-89817,\nCVE-2026-89818, CVE-2026-89819, CVE-2026-89820, CVE-2026-89821,\nCVE-2026-89822, CVE-2026-89823, CVE-2026-89824, CVE-2026-89825,\nCVE-2026-89826, CVE-2026-89827, CVE-2026-89828, CVE-2026-89829,\nCVE-2026-89830, CVE-2026-89831, CVE-2026-89832, CVE-2026-89833,\nCVE-2026-89834, CVE-2026-89835, CVE-2026-89836, CVE-2026-89837,\nCVE-2026-89838, CVE-2026-89839, CVE-2026-89840, CVE-2026-89841,\nCVE-2026-89842, CVE-2026-89843, CVE-2026-89844, CVE-2026-89845,\nCVE-2026-89846, CVE-2026-89847, CVE-2026-89848, CVE-2026-89849,\nCVE-2026-89850, CVE-2026-89851, CVE-2026-89852, CVE-2026-89853,\nCVE-2026-89854, CVE-2026-89855, CVE-2026-89856, CVE-2026-89857,\nCVE-2026-89858, CVE-2026-89859, CVE-2026-89860, CVE-2026-89861,\nCVE-2026-89862, CVE-2026-89863, CVE-2026-89864, CVE-2026-89865,\nCVE-2026-89866, CVE-2026-89867, CVE-2026-89868, CVE-2026-89869,\nCVE-2026-89870, CVE-2026-89871, CVE-2026-89872, CVE-2026-89873,\nCVE-2026-89874, CVE-2026-89875, CVE-2026-89876, CVE-2026-89877,\nCVE-2026-89878, CVE-2026-89879, CVE-2026-89880, CVE-2026-89881,\nCVE-2026-89882, CVE-2026-89883, CVE-2026-89884, CVE-2026-89885,\nCVE-2026-89886, CVE-2026-89887, CVE-2026-89888, CVE-2026-89889,\nCVE-2026-89890, CVE-2026-89891, CVE-2026-89892, CVE-2026-89893,\nCVE-2026-89894, CVE-2026-89895, CVE-2026-89896, CVE-2026-89897,\nCVE-2026-89898, CVE-2026-89899, CVE-2026-89901, CVE-2026-89902,\nCVE-2026-89903, CVE-2026-89904, CVE-2026-89905, CVE-2026-89906,\nCVE-2026-89908, CVE-2026-89909, CVE-2026-89911, CVE-2026-89912,\nCVE-2026-89913, CVE-2026-89914, CVE-2026-89915, CVE-2026-89916,\nCVE-2026-89917, CVE-2026-89918, CVE-2026-89919, CVE-2026-89920,\nCVE-2026-89921, CVE-2026-89922, CVE-2026-89923, CVE-2026-89924,\nCVE-2026-89925, CVE-2026-89926, CVE-2026-89927, CVE-2026-89928,\nCVE-2026-89929, CVE-2026-89930, CVE-2026-89931, CVE-2026-89932,\nCVE-2026-89933, CVE-2026-89934, CVE-2026-89935, CVE-2026-89936,\nCVE-2026-89937, CVE-2026-89938, CVE-2026-89939, CVE-2026-89940,\nCVE-2026-89941, CVE-2026-89942, CVE-2026-89944, CVE-2026-89945,\nCVE-2026-89946, CVE-2026-89947, CVE-2026-89948, CVE-2026-89949,\nCVE-2026-89950, CVE-2026-89951, CVE-2026-89952, CVE-2026-89953,\nCVE-2026-89954, CVE-2026-89955, CVE-2026-89956, CVE-2026-89957,\nCVE-2026-89958, CVE-2026-89959, CVE-2026-89960, CVE-2026-89961,\nCVE-2026-89962, CVE-2026-89963, CVE-2026-89964, CVE-2026-89965,\nCVE-2026-89966, CVE-2026-89967, CVE-2026-89968, CVE-2026-89969,\nCVE-2026-89970, CVE-2026-89971, CVE-2026-89972, CVE-2026-89973,\nCVE-2026-89974, CVE-2026-89975, CVE-2026-89976, CVE-2026-89977,\nCVE-2026-89978, CVE-2026-89979, CVE-2026-89981, CVE-2026-89982,\nCVE-2026-89983, CVE-2026-89984, CVE-2026-89986, CVE-2026-89987,\nCVE-2026-89988, CVE-2026-89989, CVE-2026-89990, CVE-2026-89991,\nCVE-2026-89992, CVE-2026-89993, CVE-2026-89994, CVE-2026-89995,\nCVE-2026-89996, CVE-2026-89997, CVE-2026-89998, CVE-2026-89999,\nCVE-2026-90000, CVE-2026-90001, CVE-2026-90002, CVE-2026-90003,\nCVE-2026-90005, CVE-2026-90006, CVE-2026-90007, CVE-2026-90008,\nCVE-2026-90011, CVE-2026-90012, CVE-2026-90013, CVE-2026-90014,\nCVE-2026-90015, CVE-2026-90016, CVE-2026-90017, CVE-2026-90018,\nCVE-2026-90019, CVE-2026-90020, CVE-2026-90021, CVE-2026-90022,\nCVE-2026-90023, CVE-2026-90024, CVE-2026-90025, CVE-2026-90026,\nCVE-2026-90027, CVE-2026-90028, CVE-2026-90029, CVE-2026-90030,\nCVE-2026-90031, CVE-2026-90032, CVE-2026-90033, CVE-2026-90034,\nCVE-2026-90035, CVE-2026-90036, CVE-2026-90037, CVE-2026-90039,\nCVE-2026-90040, CVE-2026-90041, CVE-2026-90042, CVE-2026-90043,\nCVE-2026-90044, CVE-2026-90045, CVE-2026-90046, CVE-2026-90047,\nCVE-2026-90048, CVE-2026-90049, CVE-2026-90051, CVE-2026-90053,\nCVE-2026-90054, CVE-2026-90055, CVE-2026-90056, CVE-2026-90057,\nCVE-2026-90058, CVE-2026-90059, CVE-2026-90060, CVE-2026-90061,\nCVE-2026-90062, CVE-2026-90063, CVE-2026-90065, CVE-2026-90066,\nCVE-2026-90067, CVE-2026-90068, CVE-2026-90069, CVE-2026-90070,\nCVE-2026-90071, CVE-2026-90072, CVE-2026-90073, CVE-2026-90074,\nCVE-2026-90075, CVE-2026-90076, CVE-2026-90077, CVE-2026-90078,\nCVE-2026-90079, CVE-2026-90080, CVE-2026-90081, CVE-2026-90082,\nCVE-2026-90083, CVE-2026-90084, CVE-2026-90085, CVE-2026-90086,\nCVE-2026-90087, CVE-2026-90088, CVE-2026-90089, CVE-2026-90090,\nCVE-2026-90091, CVE-2026-90092, CVE-2026-90093, CVE-2026-90094,\nCVE-2026-90095, CVE-2026-90097, CVE-2026-90099, CVE-2026-90100,\nCVE-2026-90101, CVE-2026-90102, CVE-2026-90103, CVE-2026-90104,\nCVE-2026-90105, CVE-2026-90106, CVE-2026-90107, CVE-2026-90108,\nCVE-2026-90109, CVE-2026-90110, CVE-2026-90111, CVE-2026-90112,\nCVE-2026-90113, CVE-2026-90114, CVE-2026-90115, CVE-2026-90116,\nCVE-2026-90119, CVE-2026-90120, CVE-2026-90121, CVE-2026-90122,\nCVE-2026-90124, CVE-2026-90125, CVE-2026-90126, CVE-2026-90127,\nCVE-2026-90128, CVE-2026-90129, CVE-2026-90130, CVE-2026-90135,\nCVE-2026-90136, CVE-2026-90137, CVE-2026-90138, CVE-2026-90139,\nCVE-2026-90140, CVE-2026-90141, CVE-2026-90142, CVE-2026-90143,\nCVE-2026-90145, CVE-2026-90146, CVE-2026-90147, CVE-2026-90148,\nCVE-2026-90149, CVE-2026-90150, CVE-2026-90151, CVE-2026-90152,\nCVE-2026-90153, CVE-2026-90154, CVE-2026-90156, CVE-2026-90157,\nCVE-2026-90158, CVE-2026-90159, CVE-2026-90160, CVE-2026-90161,\nCVE-2026-90163, CVE-2026-90164, CVE-2026-90165, CVE-2026-90166,\nCVE-2026-90169, CVE-2026-90170, CVE-2026-90174, CVE-2026-90175,\nCVE-2026-90176, CVE-2026-90177, CVE-2026-90178, CVE-2026-90179,\nCVE-2026-90180, CVE-2026-90182, CVE-2026-90183, CVE-2026-90184,\nCVE-2026-90185, CVE-2026-90186, CVE-2026-90187, CVE-2026-90188,\nCVE-2026-90189, CVE-2026-90190, CVE-2026-90191, CVE-2026-90192,\nCVE-2026-90193, CVE-2026-90194, CVE-2026-90195, CVE-2026-90196,\nCVE-2026-90197, CVE-2026-90198, CVE-2026-90199, CVE-2026-90200,\nCVE-2026-90201, CVE-2026-90202, CVE-2026-90203, CVE-2026-90204,\nCVE-2026-90205, CVE-2026-90206, CVE-2026-90207, CVE-2026-90208,\nCVE-2026-90209, CVE-2026-90211, CVE-2026-90212, CVE-2026-90213,\nCVE-2026-90214, CVE-2026-90215, CVE-2026-90216, CVE-2026-90217,\nCVE-2026-90218, CVE-2026-90219, CVE-2026-90220, CVE-2026-90221,\nCVE-2026-90222, CVE-2026-90223, CVE-2026-90224, CVE-2026-90225,\nCVE-2026-90226, CVE-2026-90227, CVE-2026-90228, CVE-2026-90229,\nCVE-2026-90230, CVE-2026-90231, CVE-2026-90232, CVE-2026-90233,\nCVE-2026-90234, CVE-2026-90235, CVE-2026-90237, CVE-2026-90240,\nCVE-2026-90241, CVE-2026-90242, CVE-2026-90243, CVE-2026-90244,\nCVE-2026-90245, CVE-2026-90246, CVE-2026-90247, CVE-2026-90248,\nCVE-2026-90249, CVE-2026-90250, CVE-2026-90251, CVE-2026-90252,\nCVE-2026-90253, CVE-2026-90254, CVE-2026-90255, CVE-2026-90256,\nCVE-2026-90257, CVE-2026-90258, CVE-2026-90259, CVE-2026-90260,\nCVE-2026-90261, CVE-2026-90262, CVE-2026-90263, CVE-2026-90264,\nCVE-2026-90265, CVE-2026-90267, CVE-2026-90269, CVE-2026-90270,\nCVE-2026-90271, CVE-2026-90272, CVE-2026-90273, CVE-2026-90274,\nCVE-2026-90275, CVE-2026-90276, CVE-2026-90277, CVE-2026-90278,\nCVE-2026-90279, CVE-2026-90280, CVE-2026-90281, CVE-2026-90282,\nCVE-2026-90283, CVE-2026-90284, CVE-2026-90285, CVE-2026-90286,\nCVE-2026-90287, CVE-2026-90288, CVE-2026-90289, CVE-2026-90290,\nCVE-2026-90291, CVE-2026-90292, CVE-2026-90293, CVE-2026-90294,\nCVE-2026-90295, CVE-2026-90296, CVE-2026-90297, CVE-2026-90298,\nCVE-2026-90300, CVE-2026-90301, CVE-2026-90302, CVE-2026-90303,\nCVE-2026-90306, CVE-2026-90307, CVE-2026-90308, CVE-2026-90309,\nCVE-2026-90311, CVE-2026-90312, CVE-2026-90313, CVE-2026-90314,\nCVE-2026-90315, CVE-2026-90316, CVE-2026-90318, CVE-2026-90319,\nCVE-2026-90320, CVE-2026-90321, CVE-2026-90322, CVE-2026-90323,\nCVE-2026-90324, CVE-2026-90325, CVE-2026-90326, CVE-2026-90327,\nCVE-2026-90328, CVE-2026-90329, CVE-2026-90330, CVE-2026-90331,\nCVE-2026-90332, CVE-2026-90333, CVE-2026-90334, CVE-2026-90335,\nCVE-2026-90336, CVE-2026-90337, CVE-2026-90338, CVE-2026-90341,\nCVE-2026-90342, CVE-2026-90343, CVE-2026-90344, CVE-2026-90345,\nCVE-2026-90346, CVE-2026-90347, CVE-2026-90348, CVE-2026-90349,\nCVE-2026-90350, CVE-2026-90351, CVE-2026-90352, CVE-2026-90353,\nCVE-2026-90354, CVE-2026-90355, CVE-2026-90356, CVE-2026-90357,\nCVE-2026-90358, CVE-2026-90359, CVE-2026-90360, CVE-2026-90361,\nCVE-2026-90362, CVE-2026-90363, CVE-2026-90364, CVE-2026-90365,\nCVE-2026-90366, CVE-2026-90367, CVE-2026-90368, CVE-2026-90369,\nCVE-2026-90370, CVE-2026-90371, CVE-2026-90372, CVE-2026-90373,\nCVE-2026-90374, CVE-2026-90375, CVE-2026-90376, CVE-2026-90377,\nCVE-2026-90378, CVE-2026-90379, CVE-2026-90380, CVE-2026-90381,\nCVE-2026-90382, CVE-2026-90383, CVE-2026-90384, CVE-2026-90385,\nCVE-2026-90386, CVE-2026-90387, CVE-2026-90388, CVE-2026-90389,\nCVE-2026-90390, CVE-2026-90391, CVE-2026-90392, CVE-2026-90393,\nCVE-2026-90394, CVE-2026-90395, CVE-2026-90396, CVE-2026-90397,\nCVE-2026-90398, CVE-2026-90399, CVE-2026-90400, CVE-2026-90401,\nCVE-2026-90402, CVE-2026-90403, CVE-2026-90404, CVE-2026-90406,\nCVE-2026-90407, CVE-2026-90408, CVE-2026-90409, CVE-2026-90410,\nCVE-2026-90411, CVE-2026-90412, CVE-2026-90413, CVE-2026-90414,\nCVE-2026-90415, CVE-2026-90416, CVE-2026-90417, CVE-2026-90418,\nCVE-2026-90419, CVE-2026-90420, CVE-2026-90421, CVE-2026-90422,\nCVE-2026-90423, CVE-2026-90424, CVE-2026-90425, CVE-2026-90426,\nCVE-2026-90427, CVE-2026-90428, CVE-2026-90429, CVE-2026-90430,\nCVE-2026-90431, CVE-2026-90433, CVE-2026-90434, CVE-2026-90435,\nCVE-2026-92476, CVE-2026-92477, CVE-2026-92479, CVE-2026-92480,\nCVE-2026-92481, CVE-2026-92482, CVE-2026-92483, CVE-2026-92484,\nCVE-2026-92485, CVE-2026-92486, CVE-2026-92488, CVE-2026-92489,\nCVE-2026-92490, CVE-2026-92491, CVE-2026-92493, CVE-2026-92494,\nCVE-2026-92495, CVE-2026-92496, CVE-2026-92497, CVE-2026-92498,\nCVE-2026-92499, CVE-2026-92500, CVE-2026-92501, CVE-2026-92503,\nCVE-2026-92504, CVE-2026-92505, CVE-2026-92506, CVE-2026-92507,\nCVE-2026-92508, CVE-2026-92509, CVE-2026-92510, CVE-2026-92511,\nCVE-2026-92512, CVE-2026-92513, CVE-2026-92514, CVE-2026-92515,\nCVE-2026-92516, CVE-2026-92517, CVE-2026-92518, CVE-2026-92519,\nCVE-2026-92520, CVE-2026-92521, CVE-2026-92522, CVE-2026-92523,\nCVE-2026-92524, CVE-2026-92525, CVE-2026-93037, CVE-2026-93039,\nCVE-2026-93040, CVE-2026-93041, CVE-2026-93042, CVE-2026-93043,\nCVE-2026-93044, CVE-2026-93045, CVE-2026-93046, CVE-2026-93047,\nCVE-2026-93048, CVE-2026-93049, CVE-2026-93050, CVE-2026-93051,\nCVE-2026-93052, CVE-2026-93053, CVE-2026-93054, CVE-2026-93055,\nCVE-2026-93056, CVE-2026-93058, CVE-2026-93059, CVE-2026-93061,\nCVE-2026-93062, CVE-2026-93063, CVE-2026-93064, CVE-2026-93065,\nCVE-2026-93066, CVE-2026-93067, CVE-2026-93068, CVE-2026-93069,\nCVE-2026-93070, CVE-2026-93071, CVE-2026-93072, CVE-2026-93073,\nCVE-2026-93077, CVE-2026-93078, CVE-2026-93079, CVE-2026-93080,\nCVE-2026-93081, CVE-2026-93082, CVE-2026-93083, CVE-2026-93084,\nCVE-2026-93085, CVE-2026-93086, CVE-2026-93089, CVE-2026-93090,\nCVE-2026-93091, CVE-2026-93092, CVE-2026-93093, CVE-2026-93094,\nCVE-2026-93095, CVE-2026-93096, CVE-2026-93097, CVE-2026-93098,\nCVE-2026-93099, CVE-2026-93100, CVE-2026-93101, CVE-2026-93102,\nCVE-2026-93103, CVE-2026-93104, CVE-2026-93105, CVE-2026-93106,\nCVE-2026-93107, CVE-2026-93108, CVE-2026-93109, CVE-2026-93110,\nCVE-2026-93112, CVE-2026-93113, CVE-2026-93114, CVE-2026-93115,\nCVE-2026-93116, CVE-2026-93117, CVE-2026-93118, CVE-2026-93119,\nCVE-2026-93120, CVE-2026-93121, CVE-2026-93122, CVE-2026-93123,\nCVE-2026-93125, CVE-2026-93126, CVE-2026-93127, CVE-2026-93128,\nCVE-2026-93129, CVE-2026-93130, CVE-2026-93131, CVE-2026-93132,\nCVE-2026-93133, CVE-2026-93134, CVE-2026-93135, CVE-2026-93136,\nCVE-2026-93137, CVE-2026-93138, CVE-2026-93140, CVE-2026-93141,\nCVE-2026-93142, CVE-2026-93143, CVE-2026-93144, CVE-2026-93145,\nCVE-2026-93146, CVE-2026-93148, CVE-2026-93149, CVE-2026-93150,\nCVE-2026-93151, CVE-2026-93152, CVE-2026-93153, CVE-2026-93154,\nCVE-2026-93155, CVE-2026-93156, CVE-2026-93157, CVE-2026-93158,\nCVE-2026-93159, CVE-2026-93160, CVE-2026-93161, CVE-2026-93162,\nCVE-2026-93163, CVE-2026-93164, CVE-2026-93165, CVE-2026-93167,\nCVE-2026-93168, CVE-2026-93169, CVE-2026-93170, CVE-2026-93172,\nCVE-2026-93173, CVE-2026-93174, CVE-2026-93176, CVE-2026-93177,\nCVE-2026-93178, CVE-2026-93179, CVE-2026-93181, CVE-2026-93182,\nCVE-2026-93183, CVE-2026-93184, CVE-2026-93185, CVE-2026-93186,\nCVE-2026-93188, CVE-2026-93189, CVE-2026-93190, CVE-2026-93191,\nCVE-2026-93192, CVE-2026-93193, CVE-2026-93194, CVE-2026-93195,\nCVE-2026-93196, CVE-2026-93198, CVE-2026-93199, CVE-2026-93200,\nCVE-2026-93201, CVE-2026-93202, CVE-2026-93203, CVE-2026-93204,\nCVE-2026-93205, CVE-2026-93206, CVE-2026-93207, CVE-2026-93208,\nCVE-2026-93209, CVE-2026-93210, CVE-2026-93211, CVE-2026-93212,\nCVE-2026-93213, CVE-2026-93214, CVE-2026-93215, CVE-2026-93216,\nCVE-2026-93217, CVE-2026-93218, CVE-2026-93219, CVE-2026-93220,\nCVE-2026-93221, CVE-2026-93222, CVE-2026-93223, CVE-2026-93224,\nCVE-2026-93225, CVE-2026-93226, CVE-2026-93227, CVE-2026-93228,\nCVE-2026-93229, CVE-2026-93230, CVE-2026-93231, CVE-2026-93233,\nCVE-2026-93234, CVE-2026-93235, CVE-2026-93236, CVE-2026-93237,\nCVE-2026-93238, CVE-2026-93239, CVE-2026-93240, CVE-2026-93241,\nCVE-2026-93242, CVE-2026-93243, CVE-2026-93244, CVE-2026-93245,\nCVE-2026-93247, CVE-2026-93248, CVE-2026-93249, CVE-2026-93250,\nCVE-2026-93251, CVE-2026-93252, CVE-2026-93253, CVE-2026-93256,\nCVE-2026-93258, CVE-2026-93259, CVE-2026-93260, CVE-2026-93261,\nCVE-2026-93262, CVE-2026-93264, CVE-2026-93265, CVE-2026-93266,\nCVE-2026-93267, CVE-2026-93268, CVE-2026-93269, CVE-2026-93270,\nCVE-2026-93271, CVE-2026-93272, CVE-2026-93273, CVE-2026-93274,\nCVE-2026-93275, CVE-2026-93276, CVE-2026-93280, CVE-2026-93281,\nCVE-2026-93282, CVE-2026-93283, CVE-2026-93284, CVE-2026-93285,\nCVE-2026-93286, CVE-2026-93287, CVE-2026-93288, CVE-2026-93781,\nCVE-2026-93782, CVE-2026-93783, CVE-2026-93784, CVE-2026-93785,\nCVE-2026-93786, CVE-2026-93787, CVE-2026-93788, CVE-2026-93789,\nCVE-2026-93790, CVE-2026-93791, CVE-2026-93792, CVE-2026-93793,\nCVE-2026-93794, CVE-2026-93795, CVE-2026-93796, CVE-2026-93797,\nCVE-2026-93798, CVE-2026-93799, CVE-2026-93800, CVE-2026-93801,\nCVE-2026-93802, CVE-2026-93803, CVE-2026-93804, CVE-2026-93805,\nCVE-2026-93806, CVE-2026-93807, CVE-2026-93808, CVE-2026-93809,\nCVE-2026-93810, CVE-2026-93811, CVE-2026-93812, CVE-2026-93813,\nCVE-2026-93814, CVE-2026-93815, CVE-2026-93816, CVE-2026-93817,\nCVE-2026-93818, CVE-2026-93819, CVE-2026-93820, CVE-2026-93821,\nCVE-2026-93822, CVE-2026-93823, CVE-2026-93824, CVE-2026-93825,\nCVE-2026-93826, CVE-2026-93827, CVE-2026-93828, CVE-2026-93829,\nCVE-2026-93830, CVE-2026-97407, CVE-2026-97408, CVE-2026-97409,\nCVE-2026-97410, CVE-2026-97411, CVE-2026-97412, CVE-2026-97413,\nCVE-2026-97414, CVE-2026-97415, CVE-2026-97416, CVE-2026-97417,\nCVE-2026-97418, CVE-2026-97419, CVE-2026-97420, CVE-2026-97421,\nCVE-2026-97422, CVE-2026-97423, CVE-2026-97424, CVE-2026-97425,\nCVE-2026-97426, CVE-2026-97427, CVE-2026-97428, CVE-2026-97429,\nCVE-2026-97430, CVE-2026-97431, CVE-2026-97432, CVE-2026-97433,\nCVE-2026-97434, CVE-2026-97435, CVE-2026-97436, CVE-2026-97437,\nCVE-2026-97438, CVE-2026-97439, CVE-2026-97440, CVE-2026-97441,\nCVE-2026-97442, CVE-2026-97443, CVE-2026-97444, CVE-2026-97445,\nCVE-2026-97446, CVE-2026-97447, CVE-2026-97448, CVE-2026-97449,\nCVE-2026-97450, CVE-2026-97451, CVE-2026-97452, CVE-2026-97453,\nCVE-2026-97454, CVE-2026-97455, CVE-2026-97456, CVE-2026-97472,\nCVE-2026-97473, CVE-2026-97474, CVE-2026-97475, CVE-2026-97476,\nCVE-2026-97477, CVE-2026-97478, CVE-2026-97479, CVE-2026-97480,\nCVE-2026-97481, CVE-2026-97482, CVE-2026-97483, CVE-2026-97484,\nCVE-2026-97485, CVE-2026-97486, CVE-2026-97487, CVE-2026-97488,\nCVE-2026-97489, CVE-2026-97490, CVE-2026-97491, CVE-2026-97492,\nCVE-2026-97493, CVE-2026-97494, CVE-2026-97495, CVE-2026-97496,\nCVE-2026-97497, CVE-2026-97498, CVE-2026-97499, CVE-2026-97500,\nCVE-2026-97501, CVE-2026-97502, CVE-2026-97503, CVE-2026-97505,\nCVE-2026-97506, CVE-2026-97507, CVE-2026-97508, CVE-2026-97509,\nCVE-2026-97510, CVE-2026-97511, CVE-2026-97512, CVE-2026-97513,\nCVE-2026-97514, CVE-2026-97515, CVE-2026-97516, CVE-2026-97517,\nCVE-2026-97518, CVE-2026-97519, CVE-2026-97520, CVE-2026-97521,\nCVE-2026-97522, CVE-2026-97523, CVE-2026-97524, CVE-2026-97525,\nCVE-2026-97526, CVE-2026-97527, CVE-2026-97528, CVE-2026-97529,\nCVE-2026-97530, CVE-2026-97531, CVE-2026-97532, CVE-2026-97533,\nCVE-2026-97534, CVE-2026-97535, CVE-2026-97536, CVE-2026-97537,\nCVE-2026-97538, CVE-2026-97539, CVE-2026-97540, CVE-2026-97541,\nCVE-2026-97542, CVE-2026-97543, CVE-2026-97544, CVE-2026-97545,\nCVE-2026-97546, CVE-2026-97547, CVE-2026-97548, CVE-2026-97549,\nCVE-2026-97550, CVE-2026-97551, CVE-2026-97552, CVE-2026-97553,\nCVE-2026-97554, CVE-2026-97555, CVE-2026-97556, CVE-2026-97557,\nCVE-2026-97558, CVE-2026-97559, CVE-2026-97560, CVE-2026-97561,\nCVE-2026-97562, CVE-2026-97563, CVE-2026-97564, CVE-2026-97565,\nCVE-2026-97566, CVE-2026-97567, CVE-2026-97568, CVE-2026-97571,\nCVE-2026-97572, CVE-2026-97573, CVE-2026-97574, CVE-2026-97575,\nCVE-2026-97576, CVE-2026-97577, CVE-2026-97578, CVE-2026-97579,\nCVE-2026-97580, CVE-2026-97581, CVE-2026-97582, CVE-2026-97583,\nCVE-2026-97584, CVE-2026-97585, CVE-2026-97586, CVE-2026-97587,\nCVE-2026-97588, CVE-2026-97589, CVE-2026-97590, CVE-2026-97591,\nCVE-2026-97592, CVE-2026-97593, CVE-2026-97594, CVE-2026-97595,\nCVE-2026-97596, CVE-2026-97597, CVE-2026-97598, CVE-2026-97599,\nCVE-2026-97600, CVE-2026-97601, CVE-2026-97602, CVE-2026-97603,\nCVE-2026-97604, CVE-2026-97605, CVE-2026-97606, CVE-2026-97607,\nCVE-2026-97608, CVE-2026-97609, CVE-2026-97610, CVE-2026-97611,\nCVE-2026-97612, CVE-2026-97613, CVE-2026-97614, CVE-2026-97615,\nCVE-2026-97616, CVE-2026-97617, CVE-2026-97618, CVE-2026-97619,\nCVE-2026-97620, CVE-2026-97621, CVE-2026-97899, CVE-2026-97900,\nCVE-2026-97901, CVE-2026-97902, CVE-2026-97903, CVE-2026-97904,\nCVE-2026-97905, CVE-2026-97906, CVE-2026-97907, CVE-2026-97908,\nCVE-2026-97909, CVE-2026-97910, CVE-2026-97912, CVE-2026-97913,\nCVE-2026-97914, CVE-2026-97915, CVE-2026-97916, CVE-2026-97917,\nCVE-2026-97918, CVE-2026-97919, CVE-2026-97920, CVE-2026-97921,\nCVE-2026-97922, CVE-2026-97923, CVE-2026-97924, CVE-2026-97925,\nCVE-2026-97926, CVE-2026-97927, CVE-2026-97928, CVE-2026-97929,\nCVE-2026-97930, CVE-2026-97931, CVE-2026-97932, CVE-2026-97933,\nCVE-2026-97934, CVE-2026-97935, CVE-2026-97936, CVE-2026-97938,\nCVE-2026-97939, CVE-2026-97940, CVE-2026-97942, CVE-2026-97943,\nCVE-2026-97944, CVE-2026-97945, CVE-2026-97946, CVE-2026-97947,\nCVE-2026-97948, CVE-2026-97950, CVE-2026-97951, CVE-2026-97953,\nCVE-2026-97954, CVE-2026-97955, CVE-2026-97956, CVE-2026-97957,\nCVE-2026-97958, CVE-2026-97959, CVE-2026-97960, CVE-2026-97961,\nCVE-2026-97962, CVE-2026-97963, CVE-2026-97964, CVE-2026-97965,\nCVE-2026-97966, CVE-2026-97967, CVE-2026-97968, CVE-2026-97969,\nCVE-2026-97970, CVE-2026-97971, CVE-2026-97972, CVE-2026-97973,\nCVE-2026-97974, CVE-2026-97975, CVE-2026-97976, CVE-2026-97977,\nCVE-2026-97978, CVE-2026-97979, CVE-2026-97981, CVE-2026-97982,\nCVE-2026-97983, CVE-2026-97984, CVE-2026-97985, CVE-2026-97986,\nCVE-2026-97987, CVE-2026-97988, CVE-2026-97989, CVE-2026-97990,\nCVE-2026-97991, CVE-2026-97992, CVE-2026-97993, CVE-2026-97994,\nCVE-2026-97995, CVE-2026-97996, CVE-2026-97997, CVE-2026-97998,\nCVE-2026-98000, CVE-2026-98001, CVE-2026-98002, CVE-2026-98003,\nCVE-2026-98004, CVE-2026-98005, CVE-2026-98006, CVE-2026-98007,\nCVE-2026-98008, CVE-2026-98009, CVE-2026-98010, CVE-2026-98011,\nCVE-2026-98012, CVE-2026-98013, CVE-2026-98014, CVE-2026-98015,\nCVE-2026-98016, CVE-2026-98017, CVE-2026-98018, CVE-2026-98019,\nCVE-2026-98020, CVE-2026-98021, CVE-2026-98022, CVE-2026-98023,\nCVE-2026-98024, CVE-2026-98025, CVE-2026-98026, CVE-2026-98027,\nCVE-2026-98028, CVE-2026-98029, CVE-2026-98030, CVE-2026-98031,\nCVE-2026-98032, CVE-2026-98033, CVE-2026-98034, CVE-2026-98037,\nCVE-2026-98039, CVE-2026-98041, CVE-2026-98043, CVE-2026-98044,\nCVE-2026-98045, CVE-2026-98046, CVE-2026-98047, CVE-2026-98048,\nCVE-2026-98049, CVE-2026-98050, CVE-2026-98051, CVE-2026-98052,\nCVE-2026-98053, CVE-2026-98054, CVE-2026-98055, CVE-2026-98056,\nCVE-2026-98057, CVE-2026-98058, CVE-2026-98059, CVE-2026-98060,\nCVE-2026-98061, CVE-2026-98062, CVE-2026-98063, CVE-2026-98064,\nCVE-2026-98065, CVE-2026-98066, CVE-2026-98067, CVE-2026-98068,\nCVE-2026-98069, CVE-2026-98070, CVE-2026-98071, CVE-2026-98072,\nCVE-2026-98073, CVE-2026-98074, CVE-2026-98075, CVE-2026-98076,\nCVE-2026-98077, CVE-2026-98078, CVE-2026-98079, CVE-2026-98080,\nCVE-2026-98081, CVE-2026-98082, CVE-2026-98083, CVE-2026-98084,\nCVE-2026-98085, CVE-2026-98086, CVE-2026-98087, CVE-2026-98088,\nCVE-2026-98089, CVE-2026-98090, CVE-2026-98091, CVE-2026-98092,\nCVE-2026-98093, CVE-2026-98094, CVE-2026-98095, CVE-2026-98096,\nCVE-2026-98097, CVE-2026-98098, CVE-2026-98099, CVE-2026-98101,\nCVE-2026-98102, CVE-2026-98103, CVE-2026-98104, CVE-2026-98105,\nCVE-2026-98106, CVE-2026-98107, CVE-2026-98108, CVE-2026-98109,\nCVE-2026-98110, CVE-2026-98111, CVE-2026-98112, CVE-2026-98113,\nCVE-2026-98114, CVE-2026-98115, CVE-2026-98116, CVE-2026-98117,\nCVE-2026-98118, CVE-2026-98119, CVE-2026-98120, CVE-2026-98121,\nCVE-2026-98122, CVE-2026-98123, CVE-2026-98124, CVE-2026-98125,\nCVE-2026-98126, CVE-2026-98127, CVE-2026-98128, CVE-2026-98129,\nCVE-2026-98130, CVE-2026-98131, CVE-2026-98134, CVE-2026-98142,\nCVE-2026-98143, CVE-2026-98146, CVE-2026-98147, CVE-2026-98148,\nCVE-2026-98149, CVE-2026-98150, CVE-2026-98151, CVE-2026-98152,\nCVE-2026-98153, CVE-2026-98154, CVE-2026-98155, CVE-2026-98156,\nCVE-2026-98157, CVE-2026-98158, CVE-2026-98159, CVE-2026-98160,\nCVE-2026-98161, CVE-2026-98162, CVE-2026-98163, CVE-2026-98164,\nCVE-2026-98166, CVE-2026-98167, CVE-2026-98168, CVE-2026-98169,\nCVE-2026-98170, CVE-2026-98171, CVE-2026-98172, CVE-2026-98173,\nCVE-2026-98174, CVE-2026-98175, CVE-2026-98176, CVE-2026-98177,\nCVE-2026-98179, CVE-2026-98180, CVE-2026-98181, CVE-2026-98182,\nCVE-2026-98184, CVE-2026-98185, CVE-2026-98186, CVE-2026-98187,\nCVE-2026-98188, CVE-2026-98189, CVE-2026-98190, CVE-2026-98191,\nCVE-2026-98192, CVE-2026-98193, CVE-2026-98194, CVE-2026-98195,\nCVE-2026-98196, CVE-2026-98197, CVE-2026-98198, CVE-2026-98199,\nCVE-2026-98200, CVE-2026-98201, CVE-2026-98202, CVE-2026-98203,\nCVE-2026-98204, CVE-2026-98205, CVE-2026-98206, CVE-2026-98207,\nCVE-2026-98208, CVE-2026-98209, CVE-2026-98210, CVE-2026-98211,\nCVE-2026-98212, CVE-2026-98213, CVE-2026-98214, CVE-2026-98215,\nCVE-2026-98216, CVE-2026-98217, CVE-2026-98218, CVE-2026-98221,\nCVE-2026-98222, CVE-2026-98223, CVE-2026-98224, CVE-2026-98226,\nCVE-2026-98227, CVE-2026-98228, CVE-2026-98229, CVE-2026-98230,\nCVE-2026-98231, CVE-2026-98232, CVE-2026-98233, CVE-2026-98234,\nCVE-2026-98235, CVE-2026-98236, CVE-2026-98237, CVE-2026-98238,\nCVE-2026-98239, CVE-2026-98240, CVE-2026-98241, CVE-2026-98242,\nCVE-2026-98244, CVE-2026-98245, CVE-2026-98246, CVE-2026-98247,\nCVE-2026-98248, CVE-2026-98249, CVE-2026-98251, CVE-2026-98252,\nCVE-2026-98253, CVE-2026-98254, CVE-2026-98255, CVE-2026-98256,\nCVE-2026-98257, CVE-2026-98258, CVE-2026-98259, CVE-2026-98260,\nCVE-2026-98261, CVE-2026-98262, CVE-2026-98263, CVE-2026-98264,\nCVE-2026-98265, CVE-2026-98266, CVE-2026-98267, CVE-2026-98268,\nCVE-2026-98269, CVE-2026-98270, CVE-2026-98271, CVE-2026-98272,\nCVE-2026-98273, CVE-2026-98274, CVE-2026-98275, CVE-2026-98276,\nCVE-2026-98277, CVE-2026-98278, CVE-2026-98279, CVE-2026-98280,\nCVE-2026-98281, CVE-2026-98282, CVE-2026-98283, CVE-2026-98284,\nCVE-2026-98285, CVE-2026-98286, CVE-2026-98287, CVE-2026-98288,\nCVE-2026-98289, CVE-2026-98290, CVE-2026-98291, CVE-2026-98292,\nCVE-2026-98293, CVE-2026-98294, CVE-2026-98295, CVE-2026-98296,\nCVE-2026-98297, CVE-2026-98298, CVE-2026-98299, CVE-2026-98300,\nCVE-2026-98301, CVE-2026-98302, CVE-2026-98303, CVE-2026-98304,\nCVE-2026-98306, CVE-2026-98307, CVE-2026-98308, CVE-2026-98309,\nCVE-2026-98311, CVE-2026-98312, CVE-2026-98314, CVE-2026-98317,\nCVE-2026-98318, CVE-2026-98319, CVE-2026-98320, CVE-2026-98321,\nCVE-2026-98322, CVE-2026-98323, CVE-2026-98324, CVE-2026-98325,\nCVE-2026-98326, CVE-2026-98327, CVE-2026-98328, CVE-2026-98329,\nCVE-2026-98330, CVE-2026-98331, CVE-2026-98332, CVE-2026-98333,\nCVE-2026-98334, CVE-2026-98335, CVE-2026-98336, CVE-2026-98337,\nCVE-2026-98338, CVE-2026-98339, CVE-2026-98340, CVE-2026-98341,\nCVE-2026-98342, CVE-2026-98343, CVE-2026-98344, CVE-2026-98345,\nCVE-2026-98346, CVE-2026-98347, CVE-2026-98348, CVE-2026-98349,\nCVE-2026-98350, CVE-2026-98351, CVE-2026-98352, CVE-2026-98354,\nCVE-2026-98355, CVE-2026-98356, CVE-2026-98357, CVE-2026-98358,\nCVE-2026-98359, CVE-2026-98360, CVE-2026-98361, CVE-2026-98362,\nCVE-2026-98363, CVE-2026-98364, CVE-2026-98365, CVE-2026-98366,\nCVE-2026-98367, CVE-2026-98368, CVE-2026-98369, CVE-2026-98370,\nCVE-2026-98371, CVE-2026-98372, CVE-2026-98373, CVE-2026-98374,\nCVE-2026-98377, CVE-2026-98378, CVE-2026-98379, CVE-2026-98380,\nCVE-2026-98381, CVE-2026-98382, CVE-2026-98383, CVE-2026-98384,\nCVE-2026-98386, CVE-2026-98387, CVE-2026-98388, CVE-2026-98389,\nCVE-2026-98390, CVE-2026-98391, CVE-2026-98392, CVE-2026-98393,\nCVE-2026-98394, CVE-2026-98398, CVE-2026-98399, CVE-2026-98400,\nCVE-2026-98401, CVE-2026-98402, CVE-2026-98403, CVE-2026-98404,\nCVE-2026-98406, CVE-2026-98407, CVE-2026-98408, CVE-2026-98409,\nCVE-2026-98410, CVE-2026-98411, CVE-2026-98412, CVE-2026-98413,\nCVE-2026-98414, CVE-2026-98415, CVE-2026-98416, CVE-2026-98417,\nCVE-2026-98419, CVE-2026-98421, CVE-2026-98422, CVE-2026-98423,\nCVE-2026-98424, CVE-2026-98425, CVE-2026-98426, CVE-2026-98427,\nCVE-2026-98428, CVE-2026-98429, CVE-2026-98430, CVE-2026-98431,\nCVE-2026-98433, CVE-2026-98434, CVE-2026-98435, CVE-2026-98436,\nCVE-2026-98437, CVE-2026-98439, CVE-2026-98440, CVE-2026-98441,\nCVE-2026-98442, CVE-2026-98443, CVE-2026-98444, CVE-2026-98445,\nCVE-2026-98446, CVE-2026-98447, CVE-2026-98448, CVE-2026-98449,\nCVE-2026-98450, CVE-2026-98451, CVE-2026-98452, CVE-2026-98453,\nCVE-2026-98454, CVE-2026-98455, CVE-2026-98456, CVE-2026-98457,\nCVE-2026-98458, CVE-2026-98459, CVE-2026-98460, CVE-2026-98461,\nCVE-2026-98462, CVE-2026-98463, CVE-2026-98464, CVE-2026-98465,\nCVE-2026-98466, CVE-2026-98467, CVE-2026-98468, CVE-2026-98469,\nCVE-2026-98470, CVE-2026-98471, CVE-2026-98472, CVE-2026-98473,\nCVE-2026-98474, CVE-2026-98475, CVE-2026-98476, CVE-2026-98477,\nCVE-2026-98478, CVE-2026-98479, CVE-2026-98480, CVE-2026-98481,\nCVE-2026-98482, CVE-2026-98483, CVE-2026-98484, CVE-2026-98485,\nCVE-2026-98486, CVE-2026-98487, CVE-2026-98488, CVE-2026-98489,\nCVE-2026-98490, CVE-2026-98491, CVE-2026-98492, CVE-2026-98493,\nCVE-2026-98494, CVE-2026-98495, CVE-2026-98496, CVE-2026-98497,\nCVE-2026-98498, CVE-2026-98499, CVE-2026-98501, CVE-2026-98502,\nCVE-2026-98503, CVE-2026-98504, CVE-2026-98505, CVE-2026-98506,\nCVE-2026-98507, CVE-2026-98508, CVE-2026-98509, CVE-2026-98510,\nCVE-2026-98511, CVE-2026-98512, CVE-2026-98513, CVE-2026-98514,\nCVE-2026-98515, CVE-2026-98516, CVE-2026-98517, CVE-2026-98518,\nCVE-2026-98519, CVE-2026-98521, CVE-2026-98522, CVE-2026-98523,\nCVE-2026-98524, CVE-2026-98525, CVE-2026-98526, CVE-2026-98527,\nCVE-2026-98528, CVE-2026-98529, CVE-2026-98530, CVE-2026-98531,\nCVE-2026-98532, CVE-2026-98533, CVE-2026-98534, CVE-2026-98535,\nCVE-2026-98536, CVE-2026-98537, CVE-2026-98538, CVE-2026-98539,\nCVE-2026-98541, CVE-2026-98542, CVE-2026-98543, CVE-2026-98544,\nCVE-2026-98545, CVE-2026-98546, CVE-2026-98547, CVE-2026-98548,\nCVE-2026-98549, CVE-2026-98550, CVE-2026-98551, CVE-2026-98552,\nCVE-2026-98553, CVE-2026-98554, CVE-2026-98555, CVE-2026-98556,\nCVE-2026-98558, CVE-2026-98559, CVE-2026-98560, CVE-2026-98561,\nCVE-2026-98562, CVE-2026-98563, CVE-2026-98564, CVE-2026-98565,\nCVE-2026-98566, CVE-2026-98567, CVE-2026-98568, CVE-2026-98569,\nCVE-2026-98570, CVE-2026-98571, CVE-2026-98572, CVE-2026-98573,\nCVE-2026-98574, CVE-2026-98575, CVE-2026-98576, CVE-2026-98577,\nCVE-2026-98578, CVE-2026-98579, CVE-2026-98580, CVE-2026-98581,\nCVE-2026-98582, CVE-2026-98583, CVE-2026-98584, CVE-2026-98585,\nCVE-2026-98586, CVE-2026-98588, CVE-2026-98589, CVE-2026-98590,\nCVE-2026-98591, CVE-2026-98592, CVE-2026-98593, CVE-2026-98594,\nCVE-2026-98595, CVE-2026-98596, CVE-2026-98597, CVE-2026-98598,\nCVE-2026-98599, CVE-2026-98601, CVE-2026-98602, CVE-2026-98603,\nCVE-2026-98604, CVE-2026-98605, CVE-2026-98606, CVE-2026-98607,\nCVE-2026-98608, CVE-2026-98609, CVE-2026-98610, CVE-2026-98611,\nCVE-2026-98612, CVE-2026-98613, CVE-2026-98614, CVE-2026-98615,\nCVE-2026-98616, CVE-2026-98617, CVE-2026-98618, CVE-2026-98620,\nCVE-2026-98621, CVE-2026-98622, CVE-2026-98623, CVE-2026-98624,\nCVE-2026-98625, CVE-2026-98626, CVE-2026-98628, CVE-2026-98629,\nCVE-2026-98630, CVE-2026-98631, CVE-2026-98632, CVE-2026-98633,\nCVE-2026-98634, CVE-2026-98635, CVE-2026-98636, CVE-2026-98637,\nCVE-2026-98638, CVE-2026-98639, CVE-2026-98640, CVE-2026-98641,\nCVE-2026-98642, CVE-2026-98643, CVE-2026-98644, CVE-2026-98646,\nCVE-2026-98647, CVE-2026-98648, CVE-2026-98649, CVE-2026-98650,\nCVE-2026-98651, CVE-2026-98652, CVE-2026-98653, CVE-2026-98867,\nCVE-2026-98868, CVE-2026-98871, CVE-2026-98872, CVE-2026-98873,\nCVE-2026-98874, CVE-2026-98875, CVE-2026-98876, CVE-2026-98877,\nCVE-2026-98878, CVE-2026-98879, CVE-2026-98880, CVE-2026-98881,\nCVE-2026-98882, CVE-2026-98883, CVE-2026-98884, CVE-2026-98885,\nCVE-2026-98886, CVE-2026-98887, CVE-2026-98888, CVE-2026-98889,\nCVE-2026-98891, CVE-2026-98892, CVE-2026-98893, CVE-2026-98894,\nCVE-2026-98895, CVE-2026-98896, CVE-2026-98897, CVE-2026-98898,\nCVE-2026-98899, CVE-2026-98900, CVE-2026-98901, CVE-2026-98902,\nCVE-2026-98903, CVE-2026-98904, CVE-2026-98905, CVE-2026-98906,\nCVE-2026-98907, CVE-2026-98908, CVE-2026-98909, CVE-2026-98910,\nCVE-2026-98911, CVE-2026-98912, CVE-2026-98913, CVE-2026-98914,\nCVE-2026-98915, CVE-2026-98916, CVE-2026-98917, CVE-2026-98918,\nCVE-2026-98919, CVE-2026-98921, CVE-2026-98923, CVE-2026-98924,\nCVE-2026-98925, CVE-2026-98926, CVE-2026-98927, CVE-2026-98928,\nCVE-2026-98929, CVE-2026-98930)\n","status":"published","published":"2026-11-03T11:03:44Z","modified":"2026-11-09T12:53:33.925621133Z","updated_at":"2026-11-09T13:25:32.592646Z"},{"id":"USN-8960-1","title":"linux-oem-7.0 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - USB Gadget drivers;\n  - Memory management;\n  - Multiple devices driver;\n  - ARM64 architecture;\n  - EROFS file system;\n  - Networking core;\n  - eXpress Data Path;\n  - ARM32 architecture;\n  - M68K architecture;\n  - MIPS architecture;\n  - OpenRISC architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Intel NPU Driver;\n  - Speakup Console Speech Driver;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Auxiliary display drivers;\n  - Drivers core;\n  - Micron PCIe SSD driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - AMD CDX bus driver;\n  - Hardware random number generator core;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DAX dirext access to differentiated memory framework;\n  - DIBS (Direct Internal Buffer Sharing) drivers;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - FireWire subsystem;\n  - ARM SCMI message protocol;\n  - ARM SCPI message protocol;\n  - Google firmware drivers;\n  - Qualcomm firmware drivers;\n  - FPGA Framework;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - HSI subsystem;\n  - Microsoft Hyper-V drivers;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Mouse) drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - Industry Pack bus drivers;\n  - IRQ chip drivers;\n  - Mailbox framework;\n  - Media drivers;\n  - MemoryStick subsystem;\n  - Multifunction device drivers;\n  - Analog Devices digital potentiometer driver;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - Amazon Nitro Secure Module driver;\n  - SGI GRU 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  - Texas Instruments network drivers;\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  - Operating Performance Points (OPP) driver;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - Mellanox platform drivers;\n  - Microsoft Surface platform drivers;\n  - x86 platform drivers;\n  - MediaTek PM domains;\n  - Power sequencing drivers;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - MPAM driver;\n  - RPMSG subsystem;\n  - Real Time Clock drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - Samsung SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thermal drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - USB DSL drivers;\n  - Cypress C67X00 USB driver;\n  - USB core drivers;\n  - DesignWare USB3 driver;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - Intel La Jolla Cove Adapter USB driver;\n  - Intel USBIO USB I/O expander driver;\n  - USB Serial drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C support driver;\n  - USB Type-C Port Controller Manager driver;\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  - ACRN Hypervisor Service Module driver;\n  - Virtio drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - 9P distributed file system;\n  - File systems infrastructure;\n  - AFS file system;\n  - BFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - debug file system;\n  - eCrypt file system;\n  - EFI Variable file system;\n  - exFAT 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  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Overlay file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UBI file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Tracing infrastructure;\n  - Kernel futex primitives;\n  - Memory Management;\n  - VLANs driver;\n  - IPv4 networking;\n  - io_uring subsystem;\n  - KProbes tracing;\n  - KVM subsystem;\n  - Live Update Orchestrator (LUO);\n  - Netfilter;\n  - Perf events;\n  - Scheduler infrastructure;\n  - Signal handling mechanism;\n  - Networking subsytem;\n  - Slab allocator;\n  - Sun RPC protocol;\n  - Vector I/O iterator library;\n  - Virtio network driver;\n  - Network traffic control;\n  - IPv6 networking;\n  - Bluetooth subsystem;\n  - IEEE 802.15.4 subsystem;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - NFC subsystem;\n  - SCTP protocol;\n  - Network sockets;\n  - TCP network protocol;\n  - User-space API (UAPI);\n  - Kernel init infrastructure;\n  - Audit subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - DMA mapping infrastructure;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - IRQ subsystem;\n  - KCOV code coverage framework;\n  - Locking primitives;\n  - Kernel module support;\n  - Namespaces infrastructure;\n  - Kernel command line parsing driver;\n  - PID allocator;\n  - printk logging mechanism;\n  - System reboot mechanism;\n  - Timer subsystem;\n  - Workqueue subsystem;\n  - Kernel build system;\n  - Heterogeneous memory management;\n  - UCS-2 string library;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - Appletalk network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Devlink API;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IEEE802154.4 network protocol;\n  - IFE protocol;\n  - IUCV driver;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - L2TP protocol;\n  - Logical Link layer;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - Netlink;\n  - Open vSwitch;\n  - Packet sockets;\n  - Phonet protocol;\n  - PSP security protocol;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - SMC sockets;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Linux Security Modules (LSM) Framework;\n  - Key management;\n  - Landlock security;\n  - SELinux security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - Generic sound devices;\n  - HD-audio driver;\n  - ESS ES18xx ALSA driver;\n  - ICE1712/ICE1724 (Envy24) ALSA driver;\n  - Digigram PCXHR ALSA driver;\n  - AMD SoC Alsa drivers;\n  - Cirrus Logic audio codecs;\n  - QCOM ASoC drivers;\n  - Realtek audio codecs;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SoC Audio for Freescale CPUs drivers;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - Amlogic Meson SoC drivers;\n  - Rockchip ASoC drivers;\n  - SoundWire (SDCA) ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - Spreadtrum ASoC drivers;\n  - STI ASoC drivers;\n  - Xilinx ASoC drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n(CVE-2026-100070, CVE-2026-100071, CVE-2026-100072, CVE-2026-100073,\nCVE-2026-100074, CVE-2026-100075, CVE-2026-100076, CVE-2026-100077,\nCVE-2026-100078, CVE-2026-100079, CVE-2026-68451, CVE-2026-68452,\nCVE-2026-68453, CVE-2026-74440, CVE-2026-74441, CVE-2026-74442,\nCVE-2026-74443, CVE-2026-74444, CVE-2026-74445, CVE-2026-74446,\nCVE-2026-74447, CVE-2026-74448, CVE-2026-74449, CVE-2026-74450,\nCVE-2026-74451, CVE-2026-74452, CVE-2026-74453, CVE-2026-74454,\nCVE-2026-74455, CVE-2026-74456, CVE-2026-74457, CVE-2026-74458,\nCVE-2026-74459, CVE-2026-74460, CVE-2026-74461, CVE-2026-74462,\nCVE-2026-74463, CVE-2026-74464, CVE-2026-74465, CVE-2026-74466,\nCVE-2026-74467, CVE-2026-74468, CVE-2026-74469, CVE-2026-74470,\nCVE-2026-74471, CVE-2026-74472, CVE-2026-74473, CVE-2026-74474,\nCVE-2026-74475, CVE-2026-74476, CVE-2026-74477, CVE-2026-74478,\nCVE-2026-74479, CVE-2026-74480, CVE-2026-74481, CVE-2026-74482,\nCVE-2026-74483, CVE-2026-74484, CVE-2026-74485, CVE-2026-74486,\nCVE-2026-74487, CVE-2026-74488, CVE-2026-74490, CVE-2026-74491,\nCVE-2026-74492, CVE-2026-74493, CVE-2026-74494, CVE-2026-74495,\nCVE-2026-74496, CVE-2026-74497, CVE-2026-74498, CVE-2026-74499,\nCVE-2026-74500, CVE-2026-74501, CVE-2026-74502, CVE-2026-74503,\nCVE-2026-74504, CVE-2026-74505, CVE-2026-74506, CVE-2026-74507,\nCVE-2026-74508, CVE-2026-74509, CVE-2026-74510, CVE-2026-74512,\nCVE-2026-74513, CVE-2026-74514, CVE-2026-74515, CVE-2026-74516,\nCVE-2026-74517, CVE-2026-74518, CVE-2026-74519, CVE-2026-74520,\nCVE-2026-74521, CVE-2026-74522, CVE-2026-74523, CVE-2026-74524,\nCVE-2026-74525, CVE-2026-74526, CVE-2026-74528, CVE-2026-74529,\nCVE-2026-74530, CVE-2026-74531, CVE-2026-74532, CVE-2026-74533,\nCVE-2026-74534, CVE-2026-74535, CVE-2026-74536, CVE-2026-74537,\nCVE-2026-74538, CVE-2026-74539, CVE-2026-74540, CVE-2026-74541,\nCVE-2026-74542, CVE-2026-74543, CVE-2026-74544, CVE-2026-74545,\nCVE-2026-74546, CVE-2026-74547, CVE-2026-74548, CVE-2026-74549,\nCVE-2026-74550, CVE-2026-74551, CVE-2026-74552, CVE-2026-74553,\nCVE-2026-74554, CVE-2026-74555, CVE-2026-74556, CVE-2026-74557,\nCVE-2026-74558, CVE-2026-74559, CVE-2026-74560, CVE-2026-74561,\nCVE-2026-74562, CVE-2026-74563, CVE-2026-74564, CVE-2026-74565,\nCVE-2026-74566, CVE-2026-74567, CVE-2026-74569, CVE-2026-74571,\nCVE-2026-74572, CVE-2026-74573, CVE-2026-74574, CVE-2026-74576,\nCVE-2026-74577, CVE-2026-74579, CVE-2026-74580, CVE-2026-74581,\nCVE-2026-74582, CVE-2026-74583, CVE-2026-74585, CVE-2026-74586,\nCVE-2026-74587, CVE-2026-74588, CVE-2026-74589, CVE-2026-74590,\nCVE-2026-74591, CVE-2026-74592, CVE-2026-74593, CVE-2026-74594,\nCVE-2026-74595, CVE-2026-74596, CVE-2026-74597, CVE-2026-74598,\nCVE-2026-74599, CVE-2026-74600, CVE-2026-74601, CVE-2026-74602,\nCVE-2026-74603, CVE-2026-74604, CVE-2026-74605, CVE-2026-74606,\nCVE-2026-74607, CVE-2026-74608, CVE-2026-74609, CVE-2026-74610,\nCVE-2026-74611, CVE-2026-74612, CVE-2026-74613, CVE-2026-74614,\nCVE-2026-74615, CVE-2026-74616, CVE-2026-74617, CVE-2026-74618,\nCVE-2026-74619, CVE-2026-74620, CVE-2026-74621, CVE-2026-74622,\nCVE-2026-74623, CVE-2026-74624, CVE-2026-74625, CVE-2026-74626,\nCVE-2026-74627, CVE-2026-74628, CVE-2026-74629, CVE-2026-74630,\nCVE-2026-74631, CVE-2026-74632, CVE-2026-74633, CVE-2026-74634,\nCVE-2026-74635, CVE-2026-74636, CVE-2026-74637, CVE-2026-74638,\nCVE-2026-74639, CVE-2026-74640, CVE-2026-74641, CVE-2026-74643,\nCVE-2026-74644, CVE-2026-74645, CVE-2026-74646, CVE-2026-74647,\nCVE-2026-74648, CVE-2026-74649, CVE-2026-74650, CVE-2026-74651,\nCVE-2026-74652, CVE-2026-74653, CVE-2026-74654, CVE-2026-74655,\nCVE-2026-74656, CVE-2026-74657, CVE-2026-74658, CVE-2026-74659,\nCVE-2026-74660, CVE-2026-74661, CVE-2026-74662, CVE-2026-74663,\nCVE-2026-74664, CVE-2026-74665, CVE-2026-74666, CVE-2026-74667,\nCVE-2026-74668, CVE-2026-74669, CVE-2026-74670, CVE-2026-74671,\nCVE-2026-74672, CVE-2026-74673, CVE-2026-74674, CVE-2026-74675,\nCVE-2026-74676, CVE-2026-74677, CVE-2026-74678, CVE-2026-74679,\nCVE-2026-74680, CVE-2026-74681, CVE-2026-74682, CVE-2026-74683,\nCVE-2026-74684, CVE-2026-74685, CVE-2026-74686, CVE-2026-74687,\nCVE-2026-74688, CVE-2026-74689, CVE-2026-74690, CVE-2026-74691,\nCVE-2026-74692, CVE-2026-74693, CVE-2026-74694, CVE-2026-74695,\nCVE-2026-74696, CVE-2026-74697, CVE-2026-74698, CVE-2026-74699,\nCVE-2026-74700, CVE-2026-74701, CVE-2026-74702, CVE-2026-74703,\nCVE-2026-74704, CVE-2026-74705, CVE-2026-74706, CVE-2026-74707,\nCVE-2026-74708, CVE-2026-74709, CVE-2026-74710, CVE-2026-74711,\nCVE-2026-74712, CVE-2026-74713, CVE-2026-74714, CVE-2026-74715,\nCVE-2026-74716, CVE-2026-74717, CVE-2026-74718, CVE-2026-74719,\nCVE-2026-74720, CVE-2026-74721, CVE-2026-74722, CVE-2026-74723,\nCVE-2026-74724, CVE-2026-74725, CVE-2026-74726, CVE-2026-74727,\nCVE-2026-74728, CVE-2026-74729, CVE-2026-74730, CVE-2026-74733,\nCVE-2026-74734, CVE-2026-74735, CVE-2026-74736, CVE-2026-74737,\nCVE-2026-74738, CVE-2026-74739, CVE-2026-74740, CVE-2026-74741,\nCVE-2026-74742, CVE-2026-74743, CVE-2026-74744, CVE-2026-74745,\nCVE-2026-74746, CVE-2026-74747, CVE-2026-74748, CVE-2026-74750,\nCVE-2026-74752, CVE-2026-74753, CVE-2026-74754, CVE-2026-80519,\nCVE-2026-80520, CVE-2026-80521, CVE-2026-80522, CVE-2026-80523,\nCVE-2026-80524, CVE-2026-80525, CVE-2026-80526, CVE-2026-80527,\nCVE-2026-80528, CVE-2026-80529, CVE-2026-80530, CVE-2026-80531,\nCVE-2026-80532, CVE-2026-80533, CVE-2026-80534, CVE-2026-80535,\nCVE-2026-80536, CVE-2026-80537, CVE-2026-80538, CVE-2026-80539,\nCVE-2026-80540, CVE-2026-80541, CVE-2026-80542, CVE-2026-80547,\nCVE-2026-80548, CVE-2026-80549, CVE-2026-80550, CVE-2026-80551,\nCVE-2026-80552, CVE-2026-80553, CVE-2026-80554, CVE-2026-80555,\nCVE-2026-80556, CVE-2026-80557, CVE-2026-80558, CVE-2026-80559,\nCVE-2026-80560, CVE-2026-80561, CVE-2026-80562, CVE-2026-80563,\nCVE-2026-80564, CVE-2026-80565, CVE-2026-80566, CVE-2026-80567,\nCVE-2026-80568, CVE-2026-80569, CVE-2026-80570, CVE-2026-80571,\nCVE-2026-80572, CVE-2026-80573, CVE-2026-80574, CVE-2026-80575,\nCVE-2026-80576, CVE-2026-80577, CVE-2026-80578, CVE-2026-80579,\nCVE-2026-80580, CVE-2026-80581, CVE-2026-80582, CVE-2026-80583,\nCVE-2026-80584, CVE-2026-80585, CVE-2026-80586, CVE-2026-80587,\nCVE-2026-80588, CVE-2026-80589, CVE-2026-80590, CVE-2026-80678,\nCVE-2026-80679, CVE-2026-80680, CVE-2026-80681, CVE-2026-80683,\nCVE-2026-80684, CVE-2026-80685, CVE-2026-80686, CVE-2026-80687,\nCVE-2026-80688, CVE-2026-80689, CVE-2026-80690, CVE-2026-80691,\nCVE-2026-80692, CVE-2026-80693, CVE-2026-80694, CVE-2026-80695,\nCVE-2026-80696, CVE-2026-80697, CVE-2026-80698, CVE-2026-80699,\nCVE-2026-80700, CVE-2026-80701, CVE-2026-80702, CVE-2026-80703,\nCVE-2026-80704, CVE-2026-80705, CVE-2026-80706, CVE-2026-80707,\nCVE-2026-80708, CVE-2026-80709, CVE-2026-80710, CVE-2026-80711,\nCVE-2026-80712, CVE-2026-80713, CVE-2026-80714, CVE-2026-80715,\nCVE-2026-80716, CVE-2026-80717, CVE-2026-80718, CVE-2026-80720,\nCVE-2026-80721, CVE-2026-80722, CVE-2026-80723, CVE-2026-80724,\nCVE-2026-80727, CVE-2026-80729, CVE-2026-80730, CVE-2026-80731,\nCVE-2026-80732, CVE-2026-80733, CVE-2026-80734, CVE-2026-80735,\nCVE-2026-80736, CVE-2026-80737, CVE-2026-80738, CVE-2026-80739,\nCVE-2026-80740, CVE-2026-80741, CVE-2026-80742, CVE-2026-80743,\nCVE-2026-80744, CVE-2026-80745, CVE-2026-80747, CVE-2026-80748,\nCVE-2026-80749, CVE-2026-80750, CVE-2026-80751, CVE-2026-80752,\nCVE-2026-80753, CVE-2026-80754, CVE-2026-80755, CVE-2026-80756,\nCVE-2026-80757, CVE-2026-80758, CVE-2026-80759, CVE-2026-80760,\nCVE-2026-80761, CVE-2026-80762, CVE-2026-80763, CVE-2026-80764,\nCVE-2026-80765, CVE-2026-80766, CVE-2026-80767, CVE-2026-80768,\nCVE-2026-80769, CVE-2026-80770, CVE-2026-80771, CVE-2026-80772,\nCVE-2026-80774, CVE-2026-80775, CVE-2026-80776, CVE-2026-80777,\nCVE-2026-80778, CVE-2026-80779, CVE-2026-80780, CVE-2026-80781,\nCVE-2026-80782, CVE-2026-80783, CVE-2026-80784, CVE-2026-80785,\nCVE-2026-80786, CVE-2026-80787, CVE-2026-80788, CVE-2026-80789,\nCVE-2026-80790, CVE-2026-80791, CVE-2026-80792, CVE-2026-80793,\nCVE-2026-80794, CVE-2026-80795, CVE-2026-80796, CVE-2026-80797,\nCVE-2026-80798, CVE-2026-80799, CVE-2026-80800, CVE-2026-80801,\nCVE-2026-80802, CVE-2026-80803, CVE-2026-80804, CVE-2026-80805,\nCVE-2026-80806, CVE-2026-80807, CVE-2026-80808, CVE-2026-80809,\nCVE-2026-80810, CVE-2026-80811, CVE-2026-80812, CVE-2026-80813,\nCVE-2026-80814, CVE-2026-80815, CVE-2026-80816, CVE-2026-80817,\nCVE-2026-80818, CVE-2026-80819, CVE-2026-80820, CVE-2026-80821,\nCVE-2026-80822, CVE-2026-80823, CVE-2026-80824, CVE-2026-80825,\nCVE-2026-80826, CVE-2026-80827, CVE-2026-80828, CVE-2026-80829,\nCVE-2026-80830, CVE-2026-80831, CVE-2026-80832, CVE-2026-80833,\nCVE-2026-80834, CVE-2026-80835, CVE-2026-80836, CVE-2026-80837,\nCVE-2026-80838, CVE-2026-80839, CVE-2026-80840, CVE-2026-80841,\nCVE-2026-80842, CVE-2026-80843, CVE-2026-80844, CVE-2026-80845,\nCVE-2026-80846, CVE-2026-80847, CVE-2026-80848, CVE-2026-80849,\nCVE-2026-80850, CVE-2026-80851, CVE-2026-80852, CVE-2026-80854,\nCVE-2026-80855, CVE-2026-80856, CVE-2026-80857, CVE-2026-80858,\nCVE-2026-80859, CVE-2026-80860, CVE-2026-80861, CVE-2026-80862,\nCVE-2026-80863, CVE-2026-80864, CVE-2026-80887, CVE-2026-80888,\nCVE-2026-80889, CVE-2026-80890, CVE-2026-80891, CVE-2026-80892,\nCVE-2026-80893, CVE-2026-80894, CVE-2026-80895, CVE-2026-80896,\nCVE-2026-80897, CVE-2026-80898, CVE-2026-80899, CVE-2026-80900,\nCVE-2026-80901, CVE-2026-80902, CVE-2026-80903, CVE-2026-80904,\nCVE-2026-80905, CVE-2026-80906, CVE-2026-80907, CVE-2026-80908,\nCVE-2026-80909, CVE-2026-80910, CVE-2026-80911, CVE-2026-80912,\nCVE-2026-80913, CVE-2026-80914, CVE-2026-80915, CVE-2026-80916,\nCVE-2026-80917, CVE-2026-80918, CVE-2026-80920, CVE-2026-80921,\nCVE-2026-80922, CVE-2026-80923, CVE-2026-80924, CVE-2026-80925,\nCVE-2026-80926, CVE-2026-80927, CVE-2026-80928, CVE-2026-80929,\nCVE-2026-80930, CVE-2026-80931, CVE-2026-80932, CVE-2026-80933,\nCVE-2026-80934, CVE-2026-80935, CVE-2026-80936, CVE-2026-80937,\nCVE-2026-80938, CVE-2026-80939, CVE-2026-80940, CVE-2026-80941,\nCVE-2026-80942, CVE-2026-80943, CVE-2026-80944, CVE-2026-80945,\nCVE-2026-80946, CVE-2026-80947, CVE-2026-80948, CVE-2026-80949,\nCVE-2026-80950, CVE-2026-80951, CVE-2026-80952, CVE-2026-80953,\nCVE-2026-80954, CVE-2026-80955, CVE-2026-80956, CVE-2026-80957,\nCVE-2026-80958, CVE-2026-80959, CVE-2026-80960, CVE-2026-80961,\nCVE-2026-80962, CVE-2026-80963, CVE-2026-80964, CVE-2026-80965,\nCVE-2026-80966, CVE-2026-80967, CVE-2026-80968, CVE-2026-80969,\nCVE-2026-80970, CVE-2026-80971, CVE-2026-80972, CVE-2026-80973,\nCVE-2026-80974, CVE-2026-80975, CVE-2026-80976, CVE-2026-80977,\nCVE-2026-80978, CVE-2026-80979, CVE-2026-80980, CVE-2026-80981,\nCVE-2026-80982, CVE-2026-80983, CVE-2026-80984, CVE-2026-80985,\nCVE-2026-80986, CVE-2026-80987, CVE-2026-80988, CVE-2026-80989,\nCVE-2026-80990, CVE-2026-80991, CVE-2026-80992, CVE-2026-80993,\nCVE-2026-80994, CVE-2026-80996, CVE-2026-80997, CVE-2026-80999,\nCVE-2026-81000, CVE-2026-81001, CVE-2026-81002, CVE-2026-81003,\nCVE-2026-81004, CVE-2026-81005, CVE-2026-81006, CVE-2026-81007,\nCVE-2026-81008, CVE-2026-81009, CVE-2026-81010, CVE-2026-81011,\nCVE-2026-81012, CVE-2026-81013, CVE-2026-81014, CVE-2026-81015,\nCVE-2026-81016, CVE-2026-81017, CVE-2026-81018, CVE-2026-89437,\nCVE-2026-89438, CVE-2026-89439, CVE-2026-89440, CVE-2026-89441,\nCVE-2026-89442, CVE-2026-89443, CVE-2026-89444, CVE-2026-89445,\nCVE-2026-89446, CVE-2026-89447, CVE-2026-89448, CVE-2026-89449,\nCVE-2026-89450, CVE-2026-89451, CVE-2026-89452, CVE-2026-89453,\nCVE-2026-89454, CVE-2026-89455, CVE-2026-89456, CVE-2026-89457,\nCVE-2026-89458, CVE-2026-89460, CVE-2026-89461, CVE-2026-89462,\nCVE-2026-89463, CVE-2026-89464, CVE-2026-89465, CVE-2026-89466,\nCVE-2026-89467, CVE-2026-89468, CVE-2026-89469, CVE-2026-89470,\nCVE-2026-89471, CVE-2026-89472, CVE-2026-89473, CVE-2026-89474,\nCVE-2026-89475, CVE-2026-89476, CVE-2026-89477, CVE-2026-89478,\nCVE-2026-89479, CVE-2026-89480, CVE-2026-89481, CVE-2026-89482,\nCVE-2026-89483, CVE-2026-89484, CVE-2026-89485, CVE-2026-89486,\nCVE-2026-89487, CVE-2026-89488, CVE-2026-89489, CVE-2026-89490,\nCVE-2026-89491, CVE-2026-89492, CVE-2026-89493, CVE-2026-89494,\nCVE-2026-89495, CVE-2026-89496, CVE-2026-89497, CVE-2026-89498,\nCVE-2026-89500, CVE-2026-89501, CVE-2026-89502, CVE-2026-89503,\nCVE-2026-89504, CVE-2026-89506, CVE-2026-89507, CVE-2026-89508,\nCVE-2026-89509, CVE-2026-89510, CVE-2026-89511, CVE-2026-89512,\nCVE-2026-89513, CVE-2026-89514, CVE-2026-89515, CVE-2026-89520,\nCVE-2026-89521, CVE-2026-89522, CVE-2026-89523, CVE-2026-89524,\nCVE-2026-89525, CVE-2026-89526, CVE-2026-89527, CVE-2026-89528,\nCVE-2026-89529, CVE-2026-89530, CVE-2026-89531, CVE-2026-89532,\nCVE-2026-89533, CVE-2026-89534, CVE-2026-89535, CVE-2026-89536,\nCVE-2026-89537, CVE-2026-89538, CVE-2026-89539, CVE-2026-89540,\nCVE-2026-89541, CVE-2026-89542, CVE-2026-89543, CVE-2026-89544,\nCVE-2026-89545, CVE-2026-89546, CVE-2026-89547, CVE-2026-89548,\nCVE-2026-89549, CVE-2026-89550, CVE-2026-89551, CVE-2026-89552,\nCVE-2026-89553, CVE-2026-89554, CVE-2026-89555, CVE-2026-89556,\nCVE-2026-89557, CVE-2026-89558, CVE-2026-89559, CVE-2026-89560,\nCVE-2026-89561, CVE-2026-89562, CVE-2026-89563, CVE-2026-89564,\nCVE-2026-89565, CVE-2026-89566, CVE-2026-89567, CVE-2026-89569,\nCVE-2026-89570, CVE-2026-89571, CVE-2026-89572, CVE-2026-89573,\nCVE-2026-89574, CVE-2026-89575, CVE-2026-89576, CVE-2026-89577,\nCVE-2026-89578, CVE-2026-89579, CVE-2026-89580, CVE-2026-89581,\nCVE-2026-89582, CVE-2026-89583, CVE-2026-89584, CVE-2026-89585,\nCVE-2026-89586, CVE-2026-89587, CVE-2026-89588, CVE-2026-89589,\nCVE-2026-89590, CVE-2026-89591, CVE-2026-89592, CVE-2026-89593,\nCVE-2026-89594, CVE-2026-89595, CVE-2026-89596, CVE-2026-89597,\nCVE-2026-89598, CVE-2026-89599, CVE-2026-89600, CVE-2026-89601,\nCVE-2026-89602, CVE-2026-89604, CVE-2026-89605, CVE-2026-89606,\nCVE-2026-89607, CVE-2026-89608, CVE-2026-89609, CVE-2026-89615,\nCVE-2026-89616, CVE-2026-89617, CVE-2026-89618, CVE-2026-89619,\nCVE-2026-89620, CVE-2026-89621, CVE-2026-89622, CVE-2026-89623,\nCVE-2026-89624, CVE-2026-89625, CVE-2026-89626, CVE-2026-89627,\nCVE-2026-89628, CVE-2026-89629, CVE-2026-89630, CVE-2026-89631,\nCVE-2026-89632, CVE-2026-89633, CVE-2026-89634, CVE-2026-89636,\nCVE-2026-89637, CVE-2026-89638, CVE-2026-89640, CVE-2026-89641,\nCVE-2026-89642, CVE-2026-89643, CVE-2026-89644, CVE-2026-89645,\nCVE-2026-89646, CVE-2026-89647, CVE-2026-89648, CVE-2026-89649,\nCVE-2026-89650, CVE-2026-89651, CVE-2026-89652, CVE-2026-89653,\nCVE-2026-89654, CVE-2026-89655, CVE-2026-89656, CVE-2026-89657,\nCVE-2026-89658, CVE-2026-89659, CVE-2026-89660, CVE-2026-89661,\nCVE-2026-89662, CVE-2026-89663, CVE-2026-89664, CVE-2026-89665,\nCVE-2026-89666, CVE-2026-89667, CVE-2026-89668, CVE-2026-89669,\nCVE-2026-89670, CVE-2026-89671, CVE-2026-89672, CVE-2026-89673,\nCVE-2026-89674, CVE-2026-89675, CVE-2026-89676, CVE-2026-89677,\nCVE-2026-89678, CVE-2026-89679, CVE-2026-89680, CVE-2026-89682,\nCVE-2026-89683, CVE-2026-89684, CVE-2026-89685, CVE-2026-89686,\nCVE-2026-89687, CVE-2026-89688, CVE-2026-89689, CVE-2026-89690,\nCVE-2026-89691, CVE-2026-89692, CVE-2026-89693, CVE-2026-89694,\nCVE-2026-89695, CVE-2026-89696, CVE-2026-89697, CVE-2026-89698,\nCVE-2026-89699, CVE-2026-89700, CVE-2026-89701, CVE-2026-89702,\nCVE-2026-89703, CVE-2026-89704, CVE-2026-89705, CVE-2026-89706,\nCVE-2026-89707, CVE-2026-89708, CVE-2026-89709, CVE-2026-89710,\nCVE-2026-89711, CVE-2026-89712, CVE-2026-89713, CVE-2026-89714,\nCVE-2026-89715, CVE-2026-89716, CVE-2026-89717, CVE-2026-89718,\nCVE-2026-89719, CVE-2026-89720, CVE-2026-89721, CVE-2026-89722,\nCVE-2026-89723, CVE-2026-89724, CVE-2026-89725, CVE-2026-89726,\nCVE-2026-89727, CVE-2026-89728, CVE-2026-89729, CVE-2026-89730,\nCVE-2026-89731, CVE-2026-89732, CVE-2026-89733, CVE-2026-89734,\nCVE-2026-89735, CVE-2026-89736, CVE-2026-89737, CVE-2026-89738,\nCVE-2026-89739, CVE-2026-89740, CVE-2026-89741, CVE-2026-89742,\nCVE-2026-89743, CVE-2026-89744, CVE-2026-89745, CVE-2026-89746,\nCVE-2026-89747, CVE-2026-89749, CVE-2026-89750, CVE-2026-89751,\nCVE-2026-89752, CVE-2026-89753, CVE-2026-89754, CVE-2026-89755,\nCVE-2026-89756, CVE-2026-89757, CVE-2026-89758, CVE-2026-89759,\nCVE-2026-89761, CVE-2026-89762, CVE-2026-89763, CVE-2026-89765,\nCVE-2026-89766, CVE-2026-89767, CVE-2026-89768, CVE-2026-89769,\nCVE-2026-89771, CVE-2026-89775, CVE-2026-89776, CVE-2026-89777,\nCVE-2026-89778, CVE-2026-89779, CVE-2026-89780, CVE-2026-89781,\nCVE-2026-89782, CVE-2026-89783, CVE-2026-89784, CVE-2026-89785,\nCVE-2026-89786, CVE-2026-89787, CVE-2026-89788, CVE-2026-89789,\nCVE-2026-89790, CVE-2026-89791, CVE-2026-89792, CVE-2026-89793,\nCVE-2026-89794, CVE-2026-89795, CVE-2026-89796, CVE-2026-89797,\nCVE-2026-89798, CVE-2026-89799, CVE-2026-89800, CVE-2026-89801,\nCVE-2026-89802, CVE-2026-89803, CVE-2026-89804, CVE-2026-89806,\nCVE-2026-89807, CVE-2026-89808, CVE-2026-89809, CVE-2026-89810,\nCVE-2026-89811, CVE-2026-89812, CVE-2026-89813, CVE-2026-89814,\nCVE-2026-89815, CVE-2026-89816, CVE-2026-89817, CVE-2026-89818,\nCVE-2026-89819, CVE-2026-89820, CVE-2026-89821, CVE-2026-89822,\nCVE-2026-89823, CVE-2026-89824, CVE-2026-89825, CVE-2026-89826,\nCVE-2026-89827, CVE-2026-89828, CVE-2026-89829, CVE-2026-89830,\nCVE-2026-89831, CVE-2026-89832, CVE-2026-89833, CVE-2026-89834,\nCVE-2026-89835, CVE-2026-89836, CVE-2026-89837, CVE-2026-89838,\nCVE-2026-89839, CVE-2026-89840, CVE-2026-89841, CVE-2026-89842,\nCVE-2026-89843, CVE-2026-89844, CVE-2026-89845, CVE-2026-89846,\nCVE-2026-89847, CVE-2026-89848, CVE-2026-89849, CVE-2026-89850,\nCVE-2026-89851, CVE-2026-89852, CVE-2026-89853, CVE-2026-89854,\nCVE-2026-89855, CVE-2026-89856, CVE-2026-89857, CVE-2026-89858,\nCVE-2026-89859, CVE-2026-89860, CVE-2026-89861, CVE-2026-89862,\nCVE-2026-89863, CVE-2026-89864, CVE-2026-89865, CVE-2026-89866,\nCVE-2026-89867, CVE-2026-89868, CVE-2026-89869, CVE-2026-89870,\nCVE-2026-89871, CVE-2026-89872, CVE-2026-89873, CVE-2026-89874,\nCVE-2026-89875, CVE-2026-89876, CVE-2026-89877, CVE-2026-89878,\nCVE-2026-89879, CVE-2026-89880, CVE-2026-89881, CVE-2026-89882,\nCVE-2026-89883, CVE-2026-89884, CVE-2026-89885, CVE-2026-89886,\nCVE-2026-89887, CVE-2026-89888, CVE-2026-89889, CVE-2026-89890,\nCVE-2026-89891, CVE-2026-89892, CVE-2026-89893, CVE-2026-89894,\nCVE-2026-89895, CVE-2026-89896, CVE-2026-89897, CVE-2026-89898,\nCVE-2026-89899, CVE-2026-89901, CVE-2026-89902, CVE-2026-89903,\nCVE-2026-89904, CVE-2026-89905, CVE-2026-89906, CVE-2026-89908,\nCVE-2026-89909, CVE-2026-89911, CVE-2026-89912, CVE-2026-89913,\nCVE-2026-89914, CVE-2026-89915, CVE-2026-89916, CVE-2026-89917,\nCVE-2026-89918, CVE-2026-89919, CVE-2026-89920, CVE-2026-89921,\nCVE-2026-89922, CVE-2026-89923, CVE-2026-89924, CVE-2026-89925,\nCVE-2026-89926, CVE-2026-89927, CVE-2026-89928, CVE-2026-89929,\nCVE-2026-89930, CVE-2026-89931, CVE-2026-89932, CVE-2026-89933,\nCVE-2026-89934, CVE-2026-89935, CVE-2026-89936, CVE-2026-89937,\nCVE-2026-89938, CVE-2026-89939, CVE-2026-89940, CVE-2026-89941,\nCVE-2026-89942, CVE-2026-89944, CVE-2026-89945, CVE-2026-89946,\nCVE-2026-89947, CVE-2026-89948, CVE-2026-89949, CVE-2026-89950,\nCVE-2026-89951, CVE-2026-89952, CVE-2026-89953, CVE-2026-89954,\nCVE-2026-89955, CVE-2026-89956, CVE-2026-89957, CVE-2026-89958,\nCVE-2026-89959, CVE-2026-89960, CVE-2026-89961, CVE-2026-89962,\nCVE-2026-89963, CVE-2026-89964, CVE-2026-89965, CVE-2026-89966,\nCVE-2026-89967, CVE-2026-89968, CVE-2026-89969, CVE-2026-89970,\nCVE-2026-89971, CVE-2026-89972, CVE-2026-89973, CVE-2026-89974,\nCVE-2026-89975, CVE-2026-89976, CVE-2026-89977, CVE-2026-89978,\nCVE-2026-89979, CVE-2026-89981, CVE-2026-89982, CVE-2026-89983,\nCVE-2026-89984, CVE-2026-89986, CVE-2026-89987, CVE-2026-89988,\nCVE-2026-89989, CVE-2026-89990, CVE-2026-89991, CVE-2026-89992,\nCVE-2026-89993, CVE-2026-89994, CVE-2026-89995, CVE-2026-89996,\nCVE-2026-89997, CVE-2026-89998, CVE-2026-89999, CVE-2026-90000,\nCVE-2026-90001, CVE-2026-90002, CVE-2026-90003, CVE-2026-90005,\nCVE-2026-90006, CVE-2026-90007, CVE-2026-90008, CVE-2026-90011,\nCVE-2026-90012, CVE-2026-90013, CVE-2026-90014, CVE-2026-90015,\nCVE-2026-90016, CVE-2026-90017, CVE-2026-90018, CVE-2026-90019,\nCVE-2026-90020, CVE-2026-90021, CVE-2026-90022, CVE-2026-90023,\nCVE-2026-90024, CVE-2026-90025, CVE-2026-90026, CVE-2026-90027,\nCVE-2026-90028, CVE-2026-90029, CVE-2026-90030, CVE-2026-90031,\nCVE-2026-90032, CVE-2026-90033, CVE-2026-90034, CVE-2026-90035,\nCVE-2026-90036, CVE-2026-90037, CVE-2026-90039, CVE-2026-90040,\nCVE-2026-90041, CVE-2026-90042, CVE-2026-90043, CVE-2026-90044,\nCVE-2026-90045, CVE-2026-90046, CVE-2026-90047, CVE-2026-90048,\nCVE-2026-90049, CVE-2026-90051, CVE-2026-90053, CVE-2026-90054,\nCVE-2026-90055, CVE-2026-90056, CVE-2026-90057, CVE-2026-90058,\nCVE-2026-90059, CVE-2026-90060, CVE-2026-90061, CVE-2026-90062,\nCVE-2026-90063, CVE-2026-90065, CVE-2026-90066, CVE-2026-90067,\nCVE-2026-90068, CVE-2026-90069, CVE-2026-90070, CVE-2026-90071,\nCVE-2026-90072, CVE-2026-90073, CVE-2026-90074, CVE-2026-90075,\nCVE-2026-90076, CVE-2026-90077, CVE-2026-90078, CVE-2026-90079,\nCVE-2026-90080, CVE-2026-90081, CVE-2026-90082, CVE-2026-90083,\nCVE-2026-90084, CVE-2026-90085, CVE-2026-90086, CVE-2026-90087,\nCVE-2026-90088, CVE-2026-90089, CVE-2026-90090, CVE-2026-90091,\nCVE-2026-90092, CVE-2026-90093, CVE-2026-90094, CVE-2026-90095,\nCVE-2026-90097, CVE-2026-90099, CVE-2026-90100, CVE-2026-90101,\nCVE-2026-90102, CVE-2026-90103, CVE-2026-90104, CVE-2026-90105,\nCVE-2026-90106, CVE-2026-90107, CVE-2026-90108, CVE-2026-90109,\nCVE-2026-90110, CVE-2026-90111, CVE-2026-90112, CVE-2026-90113,\nCVE-2026-90114, CVE-2026-90115, CVE-2026-90116, CVE-2026-90119,\nCVE-2026-90120, CVE-2026-90121, CVE-2026-90122, CVE-2026-90124,\nCVE-2026-90125, CVE-2026-90126, CVE-2026-90127, CVE-2026-90128,\nCVE-2026-90129, CVE-2026-90130, CVE-2026-90135, CVE-2026-90136,\nCVE-2026-90137, CVE-2026-90138, CVE-2026-90139, CVE-2026-90140,\nCVE-2026-90141, CVE-2026-90142, CVE-2026-90143, CVE-2026-90145,\nCVE-2026-90146, CVE-2026-90147, CVE-2026-90148, CVE-2026-90149,\nCVE-2026-90150, CVE-2026-90151, CVE-2026-90152, CVE-2026-90153,\nCVE-2026-90154, CVE-2026-90156, CVE-2026-90157, CVE-2026-90158,\nCVE-2026-90159, CVE-2026-90160, CVE-2026-90161, CVE-2026-90163,\nCVE-2026-90164, CVE-2026-90165, CVE-2026-90166, CVE-2026-90169,\nCVE-2026-90170, CVE-2026-90174, CVE-2026-90175, CVE-2026-90176,\nCVE-2026-90177, CVE-2026-90178, CVE-2026-90179, CVE-2026-90180,\nCVE-2026-90182, CVE-2026-90183, CVE-2026-90184, CVE-2026-90185,\nCVE-2026-90186, CVE-2026-90187, CVE-2026-90188, CVE-2026-90189,\nCVE-2026-90190, CVE-2026-90191, CVE-2026-90192, CVE-2026-90193,\nCVE-2026-90194, CVE-2026-90195, CVE-2026-90196, CVE-2026-90197,\nCVE-2026-90198, CVE-2026-90199, CVE-2026-90200, CVE-2026-90201,\nCVE-2026-90202, CVE-2026-90203, CVE-2026-90204, CVE-2026-90205,\nCVE-2026-90206, CVE-2026-90207, CVE-2026-90208, CVE-2026-90209,\nCVE-2026-90211, CVE-2026-90212, CVE-2026-90213, CVE-2026-90214,\nCVE-2026-90215, CVE-2026-90216, CVE-2026-90217, CVE-2026-90218,\nCVE-2026-90219, CVE-2026-90220, CVE-2026-90221, CVE-2026-90222,\nCVE-2026-90223, CVE-2026-90224, CVE-2026-90225, CVE-2026-90226,\nCVE-2026-90227, CVE-2026-90228, CVE-2026-90229, CVE-2026-90230,\nCVE-2026-90231, CVE-2026-90232, CVE-2026-90233, CVE-2026-90234,\nCVE-2026-90235, CVE-2026-90237, CVE-2026-90240, CVE-2026-90241,\nCVE-2026-90242, CVE-2026-90243, CVE-2026-90244, CVE-2026-90245,\nCVE-2026-90246, CVE-2026-90247, CVE-2026-90248, CVE-2026-90249,\nCVE-2026-90250, CVE-2026-90251, CVE-2026-90252, CVE-2026-90253,\nCVE-2026-90254, CVE-2026-90255, CVE-2026-90256, CVE-2026-90257,\nCVE-2026-90258, CVE-2026-90259, CVE-2026-90260, CVE-2026-90261,\nCVE-2026-90262, CVE-2026-90263, CVE-2026-90264, CVE-2026-90265,\nCVE-2026-90267, CVE-2026-90269, CVE-2026-90270, CVE-2026-90271,\nCVE-2026-90272, CVE-2026-90273, CVE-2026-90274, CVE-2026-90275,\nCVE-2026-90276, CVE-2026-90277, CVE-2026-90278, CVE-2026-90279,\nCVE-2026-90280, CVE-2026-90281, CVE-2026-90282, CVE-2026-90283,\nCVE-2026-90284, CVE-2026-90285, CVE-2026-90286, CVE-2026-90287,\nCVE-2026-90288, CVE-2026-90289, CVE-2026-90290, CVE-2026-90291,\nCVE-2026-90292, CVE-2026-90293, CVE-2026-90294, CVE-2026-90295,\nCVE-2026-90296, CVE-2026-90297, CVE-2026-90298, CVE-2026-90300,\nCVE-2026-90301, CVE-2026-90302, CVE-2026-90303, CVE-2026-90306,\nCVE-2026-90307, CVE-2026-90308, CVE-2026-90309, CVE-2026-90311,\nCVE-2026-90312, CVE-2026-90313, CVE-2026-90314, CVE-2026-90315,\nCVE-2026-90316, CVE-2026-90318, CVE-2026-90319, CVE-2026-90320,\nCVE-2026-90321, CVE-2026-90322, CVE-2026-90323, CVE-2026-90324,\nCVE-2026-90325, CVE-2026-90326, CVE-2026-90327, CVE-2026-90328,\nCVE-2026-90329, CVE-2026-90330, CVE-2026-90331, CVE-2026-90332,\nCVE-2026-90333, CVE-2026-90334, CVE-2026-90335, CVE-2026-90336,\nCVE-2026-90337, CVE-2026-90338, CVE-2026-90341, CVE-2026-90342,\nCVE-2026-90343, CVE-2026-90344, CVE-2026-90345, CVE-2026-90346,\nCVE-2026-90347, CVE-2026-90348, CVE-2026-90349, CVE-2026-90350,\nCVE-2026-90351, CVE-2026-90352, CVE-2026-90353, CVE-2026-90354,\nCVE-2026-90355, CVE-2026-90356, CVE-2026-90357, CVE-2026-90358,\nCVE-2026-90359, CVE-2026-90360, CVE-2026-90361, CVE-2026-90362,\nCVE-2026-90363, CVE-2026-90364, CVE-2026-90365, CVE-2026-90366,\nCVE-2026-90367, CVE-2026-90368, CVE-2026-90369, CVE-2026-90370,\nCVE-2026-90371, CVE-2026-90372, CVE-2026-90373, CVE-2026-90374,\nCVE-2026-90375, CVE-2026-90376, CVE-2026-90377, CVE-2026-90378,\nCVE-2026-90379, CVE-2026-90380, CVE-2026-90381, CVE-2026-90382,\nCVE-2026-90383, CVE-2026-90384, CVE-2026-90385, CVE-2026-90386,\nCVE-2026-90387, CVE-2026-90388, CVE-2026-90389, CVE-2026-90390,\nCVE-2026-90391, CVE-2026-90392, CVE-2026-90393, CVE-2026-90394,\nCVE-2026-90395, CVE-2026-90396, CVE-2026-90397, CVE-2026-90398,\nCVE-2026-90399, CVE-2026-90400, CVE-2026-90401, CVE-2026-90402,\nCVE-2026-90403, CVE-2026-90404, CVE-2026-90406, CVE-2026-90407,\nCVE-2026-90408, CVE-2026-90409, CVE-2026-90410, CVE-2026-90411,\nCVE-2026-90412, CVE-2026-90413, CVE-2026-90414, CVE-2026-90415,\nCVE-2026-90416, CVE-2026-90417, CVE-2026-90418, CVE-2026-90419,\nCVE-2026-90420, CVE-2026-90421, CVE-2026-90422, CVE-2026-90423,\nCVE-2026-90424, CVE-2026-90425, CVE-2026-90426, CVE-2026-90427,\nCVE-2026-90428, CVE-2026-90429, CVE-2026-90430, CVE-2026-90431,\nCVE-2026-90433, CVE-2026-90434, CVE-2026-90435, CVE-2026-92476,\nCVE-2026-92477, CVE-2026-92479, CVE-2026-92480, CVE-2026-92481,\nCVE-2026-92482, CVE-2026-92483, CVE-2026-92484, CVE-2026-92485,\nCVE-2026-92486, CVE-2026-92488, CVE-2026-92489, CVE-2026-92490,\nCVE-2026-92491, CVE-2026-92493, CVE-2026-92494, CVE-2026-92495,\nCVE-2026-92496, CVE-2026-92497, CVE-2026-92498, CVE-2026-92499,\nCVE-2026-92500, CVE-2026-92501, CVE-2026-92503, CVE-2026-92504,\nCVE-2026-92505, CVE-2026-92506, CVE-2026-92507, CVE-2026-92508,\nCVE-2026-92509, CVE-2026-92510, CVE-2026-92511, CVE-2026-92512,\nCVE-2026-92513, CVE-2026-92514, CVE-2026-92515, CVE-2026-92516,\nCVE-2026-92517, CVE-2026-92518, CVE-2026-92519, CVE-2026-92520,\nCVE-2026-92521, CVE-2026-92522, CVE-2026-92523, CVE-2026-92524,\nCVE-2026-92525, CVE-2026-93037, CVE-2026-93039, CVE-2026-93040,\nCVE-2026-93041, CVE-2026-93042, CVE-2026-93043, CVE-2026-93044,\nCVE-2026-93045, CVE-2026-93046, CVE-2026-93047, CVE-2026-93048,\nCVE-2026-93049, CVE-2026-93050, CVE-2026-93051, CVE-2026-93052,\nCVE-2026-93053, CVE-2026-93054, CVE-2026-93055, CVE-2026-93056,\nCVE-2026-93058, CVE-2026-93059, CVE-2026-93061, CVE-2026-93062,\nCVE-2026-93063, CVE-2026-93064, CVE-2026-93065, CVE-2026-93066,\nCVE-2026-93067, CVE-2026-93068, CVE-2026-93069, CVE-2026-93070,\nCVE-2026-93071, CVE-2026-93072, CVE-2026-93073, CVE-2026-93077,\nCVE-2026-93078, CVE-2026-93079, CVE-2026-93080, CVE-2026-93081,\nCVE-2026-93082, CVE-2026-93083, CVE-2026-93084, CVE-2026-93085,\nCVE-2026-93086, CVE-2026-93089, CVE-2026-93090, CVE-2026-93091,\nCVE-2026-93092, CVE-2026-93093, CVE-2026-93094, CVE-2026-93095,\nCVE-2026-93096, CVE-2026-93097, CVE-2026-93098, CVE-2026-93099,\nCVE-2026-93100, CVE-2026-93101, CVE-2026-93102, CVE-2026-93103,\nCVE-2026-93104, CVE-2026-93105, CVE-2026-93106, CVE-2026-93107,\nCVE-2026-93108, CVE-2026-93109, CVE-2026-93110, CVE-2026-93112,\nCVE-2026-93113, CVE-2026-93114, CVE-2026-93115, CVE-2026-93116,\nCVE-2026-93117, CVE-2026-93118, CVE-2026-93119, CVE-2026-93120,\nCVE-2026-93121, CVE-2026-93122, CVE-2026-93123, CVE-2026-93125,\nCVE-2026-93126, CVE-2026-93127, CVE-2026-93128, CVE-2026-93129,\nCVE-2026-93130, CVE-2026-93131, CVE-2026-93132, CVE-2026-93133,\nCVE-2026-93134, CVE-2026-93135, CVE-2026-93136, CVE-2026-93137,\nCVE-2026-93138, CVE-2026-93140, CVE-2026-93141, CVE-2026-93142,\nCVE-2026-93143, CVE-2026-93144, CVE-2026-93145, CVE-2026-93146,\nCVE-2026-93148, CVE-2026-93149, CVE-2026-93150, CVE-2026-93151,\nCVE-2026-93152, CVE-2026-93153, CVE-2026-93154, CVE-2026-93155,\nCVE-2026-93156, CVE-2026-93157, CVE-2026-93158, CVE-2026-93159,\nCVE-2026-93160, CVE-2026-93161, CVE-2026-93162, CVE-2026-93163,\nCVE-2026-93164, CVE-2026-93165, CVE-2026-93167, CVE-2026-93168,\nCVE-2026-93169, CVE-2026-93170, CVE-2026-93172, CVE-2026-93173,\nCVE-2026-93174, CVE-2026-93176, CVE-2026-93177, CVE-2026-93178,\nCVE-2026-93179, CVE-2026-93181, CVE-2026-93182, CVE-2026-93183,\nCVE-2026-93184, CVE-2026-93185, CVE-2026-93186, CVE-2026-93188,\nCVE-2026-93189, CVE-2026-93190, CVE-2026-93191, CVE-2026-93192,\nCVE-2026-93193, CVE-2026-93194, CVE-2026-93195, CVE-2026-93196,\nCVE-2026-93198, CVE-2026-93199, CVE-2026-93200, CVE-2026-93201,\nCVE-2026-93202, CVE-2026-93203, CVE-2026-93204, CVE-2026-93205,\nCVE-2026-93206, CVE-2026-93207, CVE-2026-93208, CVE-2026-93209,\nCVE-2026-93210, CVE-2026-93211, CVE-2026-93212, CVE-2026-93213,\nCVE-2026-93214, CVE-2026-93215, CVE-2026-93216, CVE-2026-93217,\nCVE-2026-93218, CVE-2026-93219, CVE-2026-93220, CVE-2026-93221,\nCVE-2026-93222, CVE-2026-93223, CVE-2026-93224, CVE-2026-93225,\nCVE-2026-93226, CVE-2026-93227, CVE-2026-93228, CVE-2026-93229,\nCVE-2026-93230, CVE-2026-93231, CVE-2026-93233, CVE-2026-93234,\nCVE-2026-93235, CVE-2026-93236, CVE-2026-93237, CVE-2026-93238,\nCVE-2026-93239, CVE-2026-93240, CVE-2026-93241, CVE-2026-93242,\nCVE-2026-93243, CVE-2026-93244, CVE-2026-93245, CVE-2026-93247,\nCVE-2026-93248, CVE-2026-93249, CVE-2026-93250, CVE-2026-93251,\nCVE-2026-93252, CVE-2026-93253, CVE-2026-93256, CVE-2026-93258,\nCVE-2026-93259, CVE-2026-93260, CVE-2026-93261, CVE-2026-93262,\nCVE-2026-93264, CVE-2026-93265, CVE-2026-93266, CVE-2026-93267,\nCVE-2026-93268, CVE-2026-93269, CVE-2026-93270, CVE-2026-93271,\nCVE-2026-93272, CVE-2026-93273, CVE-2026-93274, CVE-2026-93275,\nCVE-2026-93276, CVE-2026-93280, CVE-2026-93281, CVE-2026-93282,\nCVE-2026-93283, CVE-2026-93284, CVE-2026-93285, CVE-2026-93286,\nCVE-2026-93287, CVE-2026-93288, CVE-2026-93781, CVE-2026-93782,\nCVE-2026-93783, CVE-2026-93784, CVE-2026-93785, CVE-2026-93786,\nCVE-2026-93787, CVE-2026-93788, CVE-2026-93789, CVE-2026-93790,\nCVE-2026-93791, CVE-2026-93792, CVE-2026-93793, CVE-2026-93794,\nCVE-2026-93795, CVE-2026-93796, CVE-2026-93797, CVE-2026-93798,\nCVE-2026-93799, CVE-2026-93800, CVE-2026-93801, CVE-2026-93802,\nCVE-2026-93803, CVE-2026-93804, CVE-2026-93805, CVE-2026-93806,\nCVE-2026-93807, CVE-2026-93808, CVE-2026-93809, CVE-2026-93810,\nCVE-2026-93811, CVE-2026-93812, CVE-2026-93813, CVE-2026-93814,\nCVE-2026-93815, CVE-2026-93816, CVE-2026-93817, CVE-2026-93818,\nCVE-2026-93819, CVE-2026-93820, CVE-2026-93821, CVE-2026-93822,\nCVE-2026-93823, CVE-2026-93824, CVE-2026-93825, CVE-2026-93826,\nCVE-2026-93827, CVE-2026-93828, CVE-2026-93829, CVE-2026-93830,\nCVE-2026-97407, CVE-2026-97408, CVE-2026-97409, CVE-2026-97410,\nCVE-2026-97411, CVE-2026-97412, CVE-2026-97413, CVE-2026-97414,\nCVE-2026-97415, CVE-2026-97416, CVE-2026-97417, CVE-2026-97418,\nCVE-2026-97419, CVE-2026-97420, CVE-2026-97421, CVE-2026-97422,\nCVE-2026-97423, CVE-2026-97424, CVE-2026-97425, CVE-2026-97426,\nCVE-2026-97427, CVE-2026-97428, CVE-2026-97429, CVE-2026-97430,\nCVE-2026-97431, CVE-2026-97432, CVE-2026-97433, CVE-2026-97434,\nCVE-2026-97435, CVE-2026-97436, CVE-2026-97437, CVE-2026-97438,\nCVE-2026-97439, CVE-2026-97440, CVE-2026-97441, CVE-2026-97442,\nCVE-2026-97443, CVE-2026-97444, CVE-2026-97445, CVE-2026-97446,\nCVE-2026-97447, CVE-2026-97448, CVE-2026-97449, CVE-2026-97450,\nCVE-2026-97451, CVE-2026-97452, CVE-2026-97453, CVE-2026-97454,\nCVE-2026-97455, CVE-2026-97456, CVE-2026-97472, CVE-2026-97473,\nCVE-2026-97474, CVE-2026-97475, CVE-2026-97476, CVE-2026-97477,\nCVE-2026-97478, CVE-2026-97479, CVE-2026-97480, CVE-2026-97481,\nCVE-2026-97482, CVE-2026-97483, CVE-2026-97484, CVE-2026-97485,\nCVE-2026-97486, CVE-2026-97487, CVE-2026-97488, CVE-2026-97489,\nCVE-2026-97490, CVE-2026-97491, CVE-2026-97492, CVE-2026-97493,\nCVE-2026-97494, CVE-2026-97495, CVE-2026-97496, CVE-2026-97497,\nCVE-2026-97498, CVE-2026-97499, CVE-2026-97500, CVE-2026-97501,\nCVE-2026-97502, CVE-2026-97503, CVE-2026-97505, CVE-2026-97506,\nCVE-2026-97507, CVE-2026-97511, CVE-2026-97512, CVE-2026-97513,\nCVE-2026-97514, CVE-2026-97515, CVE-2026-97516, CVE-2026-97517,\nCVE-2026-97518, CVE-2026-97519, CVE-2026-97520, CVE-2026-97521,\nCVE-2026-97522, CVE-2026-97523, CVE-2026-97524, CVE-2026-97525,\nCVE-2026-97526, CVE-2026-97527, CVE-2026-97528, CVE-2026-97529,\nCVE-2026-97530, CVE-2026-97531, CVE-2026-97532, CVE-2026-97533,\nCVE-2026-97534, CVE-2026-97535, CVE-2026-97536, CVE-2026-97537,\nCVE-2026-97538, CVE-2026-97539, CVE-2026-97540, CVE-2026-97541,\nCVE-2026-97542, CVE-2026-97543, CVE-2026-97544, CVE-2026-97545,\nCVE-2026-97546, CVE-2026-97547, CVE-2026-97548, CVE-2026-97549,\nCVE-2026-97550, CVE-2026-97551, CVE-2026-97552, CVE-2026-97553,\nCVE-2026-97554, CVE-2026-97555, CVE-2026-97556, CVE-2026-97557,\nCVE-2026-97558, CVE-2026-97559, CVE-2026-97560, CVE-2026-97561,\nCVE-2026-97562, CVE-2026-97563, CVE-2026-97564, CVE-2026-97565,\nCVE-2026-97566, CVE-2026-97567, CVE-2026-97568, CVE-2026-97571,\nCVE-2026-97572, CVE-2026-97573, CVE-2026-97574, CVE-2026-97575,\nCVE-2026-97576, CVE-2026-97577, CVE-2026-97578, CVE-2026-97579,\nCVE-2026-97580, CVE-2026-97581, CVE-2026-97582, CVE-2026-97583,\nCVE-2026-97584, CVE-2026-97585, CVE-2026-97586, CVE-2026-97587,\nCVE-2026-97588, CVE-2026-97589, CVE-2026-97590, CVE-2026-97591,\nCVE-2026-97592, CVE-2026-97593, CVE-2026-97594, CVE-2026-97595,\nCVE-2026-97596, CVE-2026-97597, CVE-2026-97598, CVE-2026-97599,\nCVE-2026-97600, CVE-2026-97601, CVE-2026-97602, CVE-2026-97603,\nCVE-2026-97604, CVE-2026-97605, CVE-2026-97606, CVE-2026-97607,\nCVE-2026-97608, CVE-2026-97609, CVE-2026-97610, CVE-2026-97611,\nCVE-2026-97612, CVE-2026-97613, CVE-2026-97614, CVE-2026-97615,\nCVE-2026-97616, CVE-2026-97617, CVE-2026-97618, CVE-2026-97619,\nCVE-2026-97620, CVE-2026-97621, CVE-2026-97899, CVE-2026-97900,\nCVE-2026-97901, CVE-2026-97902, CVE-2026-97903, CVE-2026-97904,\nCVE-2026-97905, CVE-2026-97906, CVE-2026-97907, CVE-2026-97908,\nCVE-2026-97909, CVE-2026-97910, CVE-2026-97912, CVE-2026-97913,\nCVE-2026-97914, CVE-2026-97915, CVE-2026-97916, CVE-2026-97917,\nCVE-2026-97918, CVE-2026-97919, CVE-2026-97920, CVE-2026-97921,\nCVE-2026-97922, CVE-2026-97923, CVE-2026-97924, CVE-2026-97925,\nCVE-2026-97926, CVE-2026-97927, CVE-2026-97928, CVE-2026-97929,\nCVE-2026-97930, CVE-2026-97931, CVE-2026-97932, CVE-2026-97933,\nCVE-2026-97934, CVE-2026-97935, CVE-2026-97936, CVE-2026-97938,\nCVE-2026-97939, CVE-2026-97940, CVE-2026-97942, CVE-2026-97943,\nCVE-2026-97944, CVE-2026-97945, CVE-2026-97946, CVE-2026-97947,\nCVE-2026-97948, CVE-2026-97950, CVE-2026-97951, CVE-2026-97953,\nCVE-2026-97954, CVE-2026-97955, CVE-2026-97956, CVE-2026-97957,\nCVE-2026-97958, CVE-2026-97959, CVE-2026-97960, CVE-2026-97961,\nCVE-2026-97962, CVE-2026-97963, CVE-2026-97964, CVE-2026-97965,\nCVE-2026-97966, CVE-2026-97967, CVE-2026-97968, CVE-2026-97969,\nCVE-2026-97970, CVE-2026-97971, CVE-2026-97972, CVE-2026-97973,\nCVE-2026-97974, CVE-2026-97975, CVE-2026-97976, CVE-2026-97977,\nCVE-2026-97978, CVE-2026-97979, CVE-2026-97981, CVE-2026-97982,\nCVE-2026-97983, CVE-2026-97984, CVE-2026-97985, CVE-2026-97986,\nCVE-2026-97987, CVE-2026-97988, CVE-2026-97989, CVE-2026-97990,\nCVE-2026-97991, CVE-2026-97992, CVE-2026-97993, CVE-2026-97994,\nCVE-2026-97995, CVE-2026-97996, CVE-2026-97997, CVE-2026-97998,\nCVE-2026-98000, CVE-2026-98001, CVE-2026-98002, CVE-2026-98003,\nCVE-2026-98004, CVE-2026-98005, CVE-2026-98006, CVE-2026-98007,\nCVE-2026-98008, CVE-2026-98009, CVE-2026-98010, CVE-2026-98011,\nCVE-2026-98012, CVE-2026-98013, CVE-2026-98014, CVE-2026-98015,\nCVE-2026-98016, CVE-2026-98017, CVE-2026-98018, CVE-2026-98019,\nCVE-2026-98020, CVE-2026-98021, CVE-2026-98022, CVE-2026-98023,\nCVE-2026-98024, CVE-2026-98025, CVE-2026-98026, CVE-2026-98027,\nCVE-2026-98028, CVE-2026-98029, CVE-2026-98030, CVE-2026-98031,\nCVE-2026-98032, CVE-2026-98033, CVE-2026-98034, CVE-2026-98037,\nCVE-2026-98039, CVE-2026-98041, CVE-2026-98043, CVE-2026-98044,\nCVE-2026-98045, CVE-2026-98046, CVE-2026-98047, CVE-2026-98048,\nCVE-2026-98049, CVE-2026-98050, CVE-2026-98051, CVE-2026-98052,\nCVE-2026-98053, CVE-2026-98054, CVE-2026-98055, CVE-2026-98056,\nCVE-2026-98057, CVE-2026-98058, CVE-2026-98059, CVE-2026-98060,\nCVE-2026-98061, CVE-2026-98062, CVE-2026-98063, CVE-2026-98064,\nCVE-2026-98065, CVE-2026-98066, CVE-2026-98067, CVE-2026-98068,\nCVE-2026-98069, CVE-2026-98070, CVE-2026-98071, CVE-2026-98072,\nCVE-2026-98073, CVE-2026-98074, CVE-2026-98075, CVE-2026-98076,\nCVE-2026-98077, CVE-2026-98078, CVE-2026-98079, CVE-2026-98080,\nCVE-2026-98081, CVE-2026-98082, CVE-2026-98083, CVE-2026-98084,\nCVE-2026-98085, CVE-2026-98086, CVE-2026-98087, CVE-2026-98088,\nCVE-2026-98089, CVE-2026-98090, CVE-2026-98091, CVE-2026-98092,\nCVE-2026-98093, CVE-2026-98094, CVE-2026-98095, CVE-2026-98096,\nCVE-2026-98097, CVE-2026-98098, CVE-2026-98099, CVE-2026-98101,\nCVE-2026-98102, CVE-2026-98103, CVE-2026-98104, CVE-2026-98105,\nCVE-2026-98106, CVE-2026-98107, CVE-2026-98108, CVE-2026-98109,\nCVE-2026-98110, CVE-2026-98111, CVE-2026-98112, CVE-2026-98113,\nCVE-2026-98114, CVE-2026-98115, CVE-2026-98116, CVE-2026-98117,\nCVE-2026-98118, CVE-2026-98119, CVE-2026-98120, CVE-2026-98121,\nCVE-2026-98122, CVE-2026-98123, CVE-2026-98124, CVE-2026-98125,\nCVE-2026-98126, CVE-2026-98127, CVE-2026-98128, CVE-2026-98129,\nCVE-2026-98130, CVE-2026-98131, CVE-2026-98134, CVE-2026-98142,\nCVE-2026-98143, CVE-2026-98146, CVE-2026-98147, CVE-2026-98148,\nCVE-2026-98149, CVE-2026-98150, CVE-2026-98151, CVE-2026-98152,\nCVE-2026-98153, CVE-2026-98154, CVE-2026-98155, CVE-2026-98156,\nCVE-2026-98157, CVE-2026-98158, CVE-2026-98159, CVE-2026-98160,\nCVE-2026-98161, CVE-2026-98162, CVE-2026-98163, CVE-2026-98164,\nCVE-2026-98166, CVE-2026-98167, CVE-2026-98168, CVE-2026-98169,\nCVE-2026-98170, CVE-2026-98171, CVE-2026-98172, CVE-2026-98173,\nCVE-2026-98174, CVE-2026-98175, CVE-2026-98176, CVE-2026-98177,\nCVE-2026-98179, CVE-2026-98180, CVE-2026-98181, CVE-2026-98182,\nCVE-2026-98184, CVE-2026-98185, CVE-2026-98186, CVE-2026-98187,\nCVE-2026-98188, CVE-2026-98189, CVE-2026-98190, CVE-2026-98191,\nCVE-2026-98192, CVE-2026-98193, CVE-2026-98194, CVE-2026-98195,\nCVE-2026-98196, CVE-2026-98197, CVE-2026-98198, CVE-2026-98199,\nCVE-2026-98200, CVE-2026-98201, CVE-2026-98202, CVE-2026-98203,\nCVE-2026-98204, CVE-2026-98205, CVE-2026-98206, CVE-2026-98207,\nCVE-2026-98208, CVE-2026-98209, CVE-2026-98210, CVE-2026-98211,\nCVE-2026-98212, CVE-2026-98213, CVE-2026-98214, CVE-2026-98215,\nCVE-2026-98216, CVE-2026-98217, CVE-2026-98218, CVE-2026-98221,\nCVE-2026-98222, CVE-2026-98223, CVE-2026-98224, CVE-2026-98226,\nCVE-2026-98227, CVE-2026-98228, CVE-2026-98229, CVE-2026-98230,\nCVE-2026-98231, CVE-2026-98232, CVE-2026-98233, CVE-2026-98234,\nCVE-2026-98235, CVE-2026-98236, CVE-2026-98237, CVE-2026-98238,\nCVE-2026-98239, CVE-2026-98240, CVE-2026-98241, CVE-2026-98242,\nCVE-2026-98244, CVE-2026-98245, CVE-2026-98246, CVE-2026-98247,\nCVE-2026-98248, CVE-2026-98249, CVE-2026-98251, CVE-2026-98252,\nCVE-2026-98253, CVE-2026-98254, CVE-2026-98255, CVE-2026-98256,\nCVE-2026-98257, CVE-2026-98258, CVE-2026-98259, CVE-2026-98260,\nCVE-2026-98261, CVE-2026-98262, CVE-2026-98263, CVE-2026-98264,\nCVE-2026-98265, CVE-2026-98266, CVE-2026-98267, CVE-2026-98268,\nCVE-2026-98269, CVE-2026-98270, CVE-2026-98271, CVE-2026-98272,\nCVE-2026-98273, CVE-2026-98274, CVE-2026-98275, CVE-2026-98276,\nCVE-2026-98277, CVE-2026-98278, CVE-2026-98279, CVE-2026-98280,\nCVE-2026-98281, CVE-2026-98282, CVE-2026-98283, CVE-2026-98284,\nCVE-2026-98285, CVE-2026-98286, CVE-2026-98287, CVE-2026-98288,\nCVE-2026-98289, CVE-2026-98290, CVE-2026-98291, CVE-2026-98292,\nCVE-2026-98293, CVE-2026-98294, CVE-2026-98295, CVE-2026-98296,\nCVE-2026-98297, CVE-2026-98298, CVE-2026-98299, CVE-2026-98300,\nCVE-2026-98301, CVE-2026-98302, CVE-2026-98303, CVE-2026-98304,\nCVE-2026-98306, CVE-2026-98307, CVE-2026-98308, CVE-2026-98309,\nCVE-2026-98311, CVE-2026-98312, CVE-2026-98314, CVE-2026-98317,\nCVE-2026-98318, CVE-2026-98319, CVE-2026-98320, CVE-2026-98321,\nCVE-2026-98322, CVE-2026-98323, CVE-2026-98324, CVE-2026-98325,\nCVE-2026-98326, CVE-2026-98327, CVE-2026-98328, CVE-2026-98329,\nCVE-2026-98330, CVE-2026-98331, CVE-2026-98332, CVE-2026-98333,\nCVE-2026-98334, CVE-2026-98335, CVE-2026-98336, CVE-2026-98337,\nCVE-2026-98338, CVE-2026-98339, CVE-2026-98340, CVE-2026-98341,\nCVE-2026-98342, CVE-2026-98343, CVE-2026-98344, CVE-2026-98345,\nCVE-2026-98346, CVE-2026-98347, CVE-2026-98348, CVE-2026-98349,\nCVE-2026-98350, CVE-2026-98351, CVE-2026-98352, CVE-2026-98354,\nCVE-2026-98355, CVE-2026-98356, CVE-2026-98357, CVE-2026-98358,\nCVE-2026-98359, CVE-2026-98360, CVE-2026-98361, CVE-2026-98362,\nCVE-2026-98363, CVE-2026-98364, CVE-2026-98365, CVE-2026-98366,\nCVE-2026-98367, CVE-2026-98368, CVE-2026-98369, CVE-2026-98370,\nCVE-2026-98371, CVE-2026-98372, CVE-2026-98373, CVE-2026-98374,\nCVE-2026-98377, CVE-2026-98378, CVE-2026-98379, CVE-2026-98380,\nCVE-2026-98381, CVE-2026-98382, CVE-2026-98383, CVE-2026-98384,\nCVE-2026-98386, CVE-2026-98387, CVE-2026-98388, CVE-2026-98389,\nCVE-2026-98390, CVE-2026-98391, CVE-2026-98392, CVE-2026-98393,\nCVE-2026-98394, CVE-2026-98398, CVE-2026-98399, CVE-2026-98400,\nCVE-2026-98401, CVE-2026-98402, CVE-2026-98403, CVE-2026-98404,\nCVE-2026-98406, CVE-2026-98407, CVE-2026-98408, CVE-2026-98409,\nCVE-2026-98410, CVE-2026-98411, CVE-2026-98412, CVE-2026-98413,\nCVE-2026-98414, CVE-2026-98415, CVE-2026-98416, CVE-2026-98417,\nCVE-2026-98419, CVE-2026-98421, CVE-2026-98422, CVE-2026-98423,\nCVE-2026-98424, CVE-2026-98425, CVE-2026-98426, CVE-2026-98427,\nCVE-2026-98428, CVE-2026-98429, CVE-2026-98430, CVE-2026-98431,\nCVE-2026-98433, CVE-2026-98434, CVE-2026-98435, CVE-2026-98436,\nCVE-2026-98437, CVE-2026-98439, CVE-2026-98440, CVE-2026-98441,\nCVE-2026-98442, CVE-2026-98443, CVE-2026-98444, CVE-2026-98445,\nCVE-2026-98446, CVE-2026-98447, CVE-2026-98448, CVE-2026-98449,\nCVE-2026-98450, CVE-2026-98451, CVE-2026-98452, CVE-2026-98453,\nCVE-2026-98454, CVE-2026-98455, CVE-2026-98456, CVE-2026-98457,\nCVE-2026-98458, CVE-2026-98459, CVE-2026-98460, CVE-2026-98461,\nCVE-2026-98462, CVE-2026-98463, CVE-2026-98464, CVE-2026-98465,\nCVE-2026-98466, CVE-2026-98467, CVE-2026-98468, CVE-2026-98469,\nCVE-2026-98470, CVE-2026-98471, CVE-2026-98472, CVE-2026-98473,\nCVE-2026-98474, CVE-2026-98475, CVE-2026-98476, CVE-2026-98477,\nCVE-2026-98478, CVE-2026-98479, CVE-2026-98480, CVE-2026-98481,\nCVE-2026-98482, CVE-2026-98483, CVE-2026-98484, CVE-2026-98485,\nCVE-2026-98486, CVE-2026-98487, CVE-2026-98488, CVE-2026-98489,\nCVE-2026-98490, CVE-2026-98491, CVE-2026-98492, CVE-2026-98493,\nCVE-2026-98494, CVE-2026-98495, CVE-2026-98496, CVE-2026-98497,\nCVE-2026-98498, CVE-2026-98499, CVE-2026-98501, CVE-2026-98502,\nCVE-2026-98503, CVE-2026-98504, CVE-2026-98505, CVE-2026-98506,\nCVE-2026-98507, CVE-2026-98508, CVE-2026-98509, CVE-2026-98510,\nCVE-2026-98511, CVE-2026-98512, CVE-2026-98513, CVE-2026-98514,\nCVE-2026-98515, CVE-2026-98516, CVE-2026-98517, CVE-2026-98518,\nCVE-2026-98519, CVE-2026-98521, CVE-2026-98522, CVE-2026-98523,\nCVE-2026-98524, CVE-2026-98525, CVE-2026-98526, CVE-2026-98527,\nCVE-2026-98528, CVE-2026-98529, CVE-2026-98530, CVE-2026-98531,\nCVE-2026-98532, CVE-2026-98533, CVE-2026-98534, CVE-2026-98535,\nCVE-2026-98536, CVE-2026-98537, CVE-2026-98538, CVE-2026-98539,\nCVE-2026-98541, CVE-2026-98542, CVE-2026-98543, CVE-2026-98544,\nCVE-2026-98545, CVE-2026-98546, CVE-2026-98547, CVE-2026-98548,\nCVE-2026-98549, CVE-2026-98550, CVE-2026-98551, CVE-2026-98552,\nCVE-2026-98553, CVE-2026-98554, CVE-2026-98555, CVE-2026-98556,\nCVE-2026-98558, CVE-2026-98559, CVE-2026-98560, CVE-2026-98561,\nCVE-2026-98562, CVE-2026-98563, CVE-2026-98564, CVE-2026-98565,\nCVE-2026-98566, CVE-2026-98567, CVE-2026-98568, CVE-2026-98569,\nCVE-2026-98570, CVE-2026-98571, CVE-2026-98572, CVE-2026-98573,\nCVE-2026-98574, CVE-2026-98575, CVE-2026-98576, CVE-2026-98577,\nCVE-2026-98578, CVE-2026-98579, CVE-2026-98580, CVE-2026-98581,\nCVE-2026-98582, CVE-2026-98583, CVE-2026-98584, CVE-2026-98585,\nCVE-2026-98586, CVE-2026-98588, CVE-2026-98589, CVE-2026-98590,\nCVE-2026-98591, CVE-2026-98592, CVE-2026-98593, CVE-2026-98594,\nCVE-2026-98595, CVE-2026-98596, CVE-2026-98597, CVE-2026-98598,\nCVE-2026-98599, CVE-2026-98601, CVE-2026-98602, CVE-2026-98603,\nCVE-2026-98604, CVE-2026-98605, CVE-2026-98606, CVE-2026-98607,\nCVE-2026-98608, CVE-2026-98609, CVE-2026-98610, CVE-2026-98611,\nCVE-2026-98612, CVE-2026-98613, CVE-2026-98614, CVE-2026-98615,\nCVE-2026-98616, CVE-2026-98617, CVE-2026-98618, CVE-2026-98620,\nCVE-2026-98621, CVE-2026-98622, CVE-2026-98623, CVE-2026-98624,\nCVE-2026-98625, CVE-2026-98626, CVE-2026-98628, CVE-2026-98629,\nCVE-2026-98630, CVE-2026-98631, CVE-2026-98632, CVE-2026-98633,\nCVE-2026-98634, CVE-2026-98635, CVE-2026-98636, CVE-2026-98637,\nCVE-2026-98638, CVE-2026-98639, CVE-2026-98640, CVE-2026-98641,\nCVE-2026-98642, CVE-2026-98643, CVE-2026-98644, CVE-2026-98646,\nCVE-2026-98647, CVE-2026-98648, CVE-2026-98649, CVE-2026-98650,\nCVE-2026-98651, CVE-2026-98652, CVE-2026-98653, CVE-2026-98867,\nCVE-2026-98868, CVE-2026-98871, CVE-2026-98872, CVE-2026-98873,\nCVE-2026-98874, CVE-2026-98875, CVE-2026-98876, CVE-2026-98877,\nCVE-2026-98878, CVE-2026-98879, CVE-2026-98880, CVE-2026-98881,\nCVE-2026-98882, CVE-2026-98883, CVE-2026-98884, CVE-2026-98885,\nCVE-2026-98886, CVE-2026-98887, CVE-2026-98888, CVE-2026-98889,\nCVE-2026-98891, CVE-2026-98892, CVE-2026-98893, CVE-2026-98894,\nCVE-2026-98895, CVE-2026-98897, CVE-2026-98898, CVE-2026-98899,\nCVE-2026-98900, CVE-2026-98901, CVE-2026-98902, CVE-2026-98903,\nCVE-2026-98904, CVE-2026-98905, CVE-2026-98906, CVE-2026-98907,\nCVE-2026-98908, CVE-2026-98909, CVE-2026-98910, CVE-2026-98911,\nCVE-2026-98912, CVE-2026-98913, CVE-2026-98914, CVE-2026-98915,\nCVE-2026-98916, CVE-2026-98917, CVE-2026-98918, CVE-2026-98919,\nCVE-2026-98921, CVE-2026-98923, CVE-2026-98924, CVE-2026-98925,\nCVE-2026-98926, CVE-2026-98927, CVE-2026-98928, CVE-2026-98929,\nCVE-2026-98930)\n","status":"published","published":"2026-11-03T11:03:02Z","modified":"2026-11-09T12:49:43.015417372Z","updated_at":"2026-11-09T13:27:42.046613Z"}]}}