{"id":"CVE-2026-80551","aliases":["AZL-97824","BELL-CVE-2026-80551","DEBIAN-CVE-2026-80551","EUVD-2026-66466","GHSA-p29x-7599-2m4p","MGASA-2026-0506","MGASA-2026-0542","OESA-2026-3707","OESA-2026-3987","OESA-2026-4357","UBUNTU-CVE-2026-80551","USN-8886-1","USN-8959-1","USN-8960-1"],"status":"published","title":"s390/vfio_ccw: Ensure first IDAW remains constant","description":"In 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.","severity":{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00142,"percentile":0.03584,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-08-26T14:37:20Z","modified":"2026-11-10T02:51:44Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.157.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.111-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.46-r0"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.191","6.6.154","6.12.105","6.18.46","7.1.10"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.105-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["7.1.10-1"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux-6.12","fixed_in":["6.12.107-1~deb12u1"],"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.157.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.103-r0"},{"fixed":"6.12.111-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.18.43-r0"},{"fixed":"6.18.46-r0"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.3.0"},{"fixed":"6.1.191"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.154"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.105"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.46"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.10"}]}]},{"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.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.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~rc6-1~exp1","7.3~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.105-1"}]}],"versions":["6.12.100-1","6.12.101-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.10-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.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.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"]},{"source":"osv","ecosystem":"Debian:12","package":"linux-6.12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.107-1~deb12u1"}]}],"versions":["6.12.100-1~deb12u1","6.12.101-1~deb12u1"]},{"source":"osv","ecosystem":"Mageia:10","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.55-1.mga10"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.30-5.mga10"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.14-31.mga10"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"drakx-installer-images","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.94-56.mga10"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"drakx-installer-images","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.94-56.mga10.nonfree"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"kmod-nvidia-current-wopengpu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"580.173.02-40.mga10.nonfree"}]}],"bundled":1146},{"source":"osv","ecosystem":"Mageia:10","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.55-1.mga10"}]}],"bundled":1146},{"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":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-337.0.0.238.oe2203sp4"}]}],"bundled":67},{"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:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1","5.4.0-1135.145~18.04.1","5.4.0-1136.146~18.04.1","5.4.0-1137.147~18.04.1","5.4.0-1139.149~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1147.157~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1153.163~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1156.166~18.04.1","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1160.170~18.04.1","5.4.0-1161.172~18.04.1","5.4.0-1162.173~18.04.1","5.4.0-1163.174~18.04.1","5.4.0-1165.176~18.04.1","5.4.0-1167.178~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1","5.4.0-1140.147~18.04.1","5.4.0-1142.149~18.04.1","5.4.0-1143.150~18.04.1","5.4.0-1145.152~18.04.1","5.4.0-1147.154~18.04.1","5.4.0-1148.155~18.04.1","5.4.0-1149.156~18.04.1","5.4.0-1150.157~18.04.1","5.4.0-1151.158~18.04.1","5.4.0-1152.159~18.04.1","5.4.0-1153.160~18.04.1","5.4.0-1154.161~18.04.1","5.4.0-1156.163~18.04.1","5.4.0-1157.164~18.04.1","5.4.0-1161.167~18.04.1","5.4.0-1162.168~18.04.1","5.4.0-1163.169~18.04.1","5.4.0-1164.170~18.04.1","5.4.0-1166.172~18.04.1","5.4.0-1167.173~18.04.1","5.4.0-1168.174~18.04.1","5.4.0-1169.175~18.04.1","5.4.0-1170.176~18.04.1","5.4.0-1171.177~18.04.1","5.4.0-1172.178~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1139.148~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.150~18.04.1","5.4.0-1142.151~18.04.1","5.4.0-1143.152~18.04.1","5.4.0-1145.154~18.04.1","5.4.0-1147.156~18.04.1","5.4.0-1148.157~18.04.1","5.4.0-1149.158~18.04.1","5.4.0-1150.159~18.04.1","5.4.0-1151.160~18.04.1","5.4.0-1152.161~18.04.1","5.4.0-1153.162~18.04.1","5.4.0-1154.163~18.04.1","5.4.0-1155.164~18.04.1","5.4.0-1156.165~18.04.1","5.4.0-1157.166~18.04.1","5.4.0-1159.168~18.04.1","5.4.0-1160.169~18.04.1","5.4.0-1161.170~18.04.1","5.4.0-1162.171~18.04.1","5.4.0-1163.172~18.04.1","5.4.0-1164.173~18.04.1","5.4.0-1165.174~18.04.1","5.4.0-1166.175~18.04.1","5.4.0-1167.176~18.04.1","5.4.0-1168.178~18.04.1","5.4.0-1169.179~18.04.1","5.4.0-1170.180~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1","5.4.0-200.220~18.04.1","5.4.0-202.222~18.04.1","5.4.0-204.224~18.04.1","5.4.0-205.225~18.04.1","5.4.0-208.228~18.04.1","5.4.0-211.231~18.04.1","5.4.0-212.232~18.04.1","5.4.0-214.234~18.04.1","5.4.0-215.235~18.04.1","5.4.0-216.236~18.04.1","5.4.0-218.238~18.04.1","5.4.0-219.239~18.04.1","5.4.0-220.240~18.04.1","5.4.0-221.241~18.04.1","5.4.0-222.242~18.04.1","5.4.0-223.243~18.04.1","5.4.0-224.244~18.04.1","5.4.0-225.245~18.04.1","5.4.0-227.247~18.04.1","5.4.0-228.248~18.04.1","5.4.0-229.249~18.04.1","5.4.0-231.251~18.04.1","5.4.0-233.253~18.04.1","5.4.0-234.254~18.04.1","5.4.0-238.258~18.04.1","5.4.0-241.261~18.04.1","5.4.0-242.262~18.04.1","5.4.0-244.264~18.04.1","5.4.0-245.265~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1","5.4.0-1082.87~18.04.1","5.4.0-1083.88~18.04.1","5.4.0-1084.89~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1092.97~18.04.1","5.4.0-1093.98~18.04.1","5.4.0-1094.99~18.04.1","5.4.0-1095.100~18.04.1","5.4.0-1096.101~18.04.1","5.4.0-1097.102~18.04.1","5.4.0-1098.103~18.04.1","5.4.0-1099.104~18.04.1","5.4.0-1100.105~18.04.1","5.4.0-1102.107~18.04.1","5.4.0-1103.108~18.04.1","5.4.0-1104.109~18.04.1","5.4.0-1105.110~18.04.1","5.4.0-1107.112~18.04.1","5.4.0-1108.113~18.04.1","5.4.0-1109.114~18.04.1","5.4.0-1111.116~18.04.1","5.4.0-1112.117~18.04.1","5.4.0-1113.118~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu: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:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.151~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1143.153~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1155.165~18.04.1","5.4.0-1156.166~18.04.2","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1159.169~18.04.1","5.4.0-1161.171~18.04.1","5.4.0-1162.172~18.04.1","5.4.0-1163.173~18.04.1","5.4.0-1164.174~18.04.1","5.4.0-1165.175~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1","5.4.0-1119.131~18.04.1","5.4.0-1120.132~18.04.1","5.4.0-1121.133~18.04.1","5.4.0-1122.134~18.04.1","5.4.0-1129.142~18.04.1","5.4.0-1130.143~18.04.1","5.4.0-1131.144~18.04.1","5.4.0-1132.145~18.04.1","5.4.0-1133.146~18.04.1","5.4.0-1134.147~18.04.1","5.4.0-1135.148~18.04.1","5.4.0-1136.149~18.04.1","5.4.0-1137.150~18.04.1","5.4.0-1139.152~18.04.1","5.4.0-1140.153~18.04.1","5.4.0-1143.156~18.04.1","5.4.0-1144.157~18.04.1","5.4.0-1145.158~18.04.1","5.4.0-1146.159~18.04.1","5.4.0-1147.160~18.04.1","5.4.0-1148.161~18.04.1","5.4.0-1149.162~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218","5.4.0-200.220","5.4.0-202.222","5.4.0-204.224","5.4.0-205.225","5.4.0-208.228","5.4.0-211.231","5.4.0-212.232","5.4.0-214.234","5.4.0-215.235","5.4.0-216.236","5.4.0-218.238","5.4.0-219.239","5.4.0-220.240","5.4.0-221.241","5.4.0-222.242","5.4.0-223.243","5.4.0-224.244","5.4.0-225.245","5.4.0-227.247","5.4.0-228.248","5.4.0-229.249","5.4.0-230.250","5.4.0-231.251","5.4.0-233.253","5.4.0-234.254","5.4.0-238.258","5.4.0-241.261","5.4.0-242.262","5.4.0-244.264","5.4.0-245.265"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1142.152","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1148.158","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1153.163","5.4.0-1154.164","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.172","5.4.0-1162.173","5.4.0-1163.174","5.4.0-1164.175","5.4.0-1165.176","5.4.0-1166.177","5.4.0-1167.178"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~20.04.1","5.15.0-1103.110~20.04.1","5.15.0-1104.111~20.04.1","5.15.0-1105.112~20.04.1","5.15.0-1106.113~20.04.1","5.15.0-1108.115~20.04.1","5.15.0-1109.116~20.04.1","5.15.0-1111.118~20.04.1","5.15.0-1112.119~20.04.1","5.15.0-1114.121~20.04.1","5.15.0-1115.122~20.04.1","5.15.0-1116.123~20.04.1","5.15.0-1117.124~20.04.1","5.15.0-1119.126~20.04.1","5.15.0-1120.127~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146","5.4.0-1140.147","5.4.0-1142.149","5.4.0-1143.150","5.4.0-1145.152","5.4.0-1147.154","5.4.0-1148.155","5.4.0-1149.156","5.4.0-1150.157","5.4.0-1151.158","5.4.0-1152.159","5.4.0-1153.160","5.4.0-1154.161","5.4.0-1156.163","5.4.0-1157.164","5.4.0-1160.166","5.4.0-1161.167","5.4.0-1162.168","5.4.0-1163.169","5.4.0-1164.170","5.4.0-1166.172","5.4.0-1167.173","5.4.0-1168.174","5.4.0-1169.175","5.4.0-1170.176","5.4.0-1171.177","5.4.0-1172.178"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1110.119~20.04.1","5.15.0-1111.120~20.04.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1123.132~20.04.1","5.15.0-1125.134~20.04.1","5.15.0-1126.135~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1","5.15.0-1081.90~20.04.1.1","5.15.0-1082.91~20.04.1.1","5.15.0-1086.95~20.04.1.1","5.15.0-1087.96~20.04.1.1","5.15.0-1088.97~20.04.1.1","5.15.0-1089.98~20.04.1.1","5.15.0-1091.100~20.04.1.1","5.15.0-1094.103~20.04.1.1","5.15.0-1096.105~20.04.1.1","5.15.0-1097.106~20.04.1.1","5.15.0-1098.107~20.04.1.1","5.15.0-1102.111~20.04.1.1","5.15.0-1103.112~20.04.1.1","5.15.0-1111.120~20.04.1.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.2","5.15.0-1118.127~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1120.129~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1124.133~20.04.1","5.15.0-1125.134~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1123.130","5.4.0-1125.132","5.4.0-1126.133"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1142.151","5.4.0-1143.152","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163","5.4.0-1155.164","5.4.0-1156.165","5.4.0-1157.166","5.4.0-1159.168","5.4.0-1160.169","5.4.0-1161.170","5.4.0-1162.171","5.4.0-1163.172","5.4.0-1164.173","5.4.0-1165.174","5.4.0-1166.175","5.4.0-1167.177","5.4.0-1168.178","5.4.0-1169.179","5.4.0-1170.180"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1104.113~20.04.1","5.15.0-1106.115~20.04.1","5.15.0-1108.117~20.04.1","5.15.0-1109.118~20.04.1","5.15.0-1111.121~20.04.1","5.15.0-1112.122~20.04.1","5.15.0-1114.124~20.04.1","5.15.0-1118.128~20.04.1","5.15.0-1120.130~20.04.1","5.15.0-1121.131~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-176.186~20.04.1","5.15.0-177.187~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-185.195~20.04.1","5.15.0-186.196~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-198.208~20.04.1","5.15.0-202.212~20.04.1","5.15.0-203.213~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86","5.4.0-1082.87","5.4.0-1083.88","5.4.0-1084.89","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1088.93","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1092.97","5.4.0-1093.98","5.4.0-1094.99","5.4.0-1095.100","5.4.0-1096.101","5.4.0-1097.102","5.4.0-1098.103","5.4.0-1099.104","5.4.0-1100.105","5.4.0-1102.107","5.4.0-1103.108","5.4.0-1104.109","5.4.0-1105.110","5.4.0-1107.112","5.4.0-1108.113","5.4.0-1109.114","5.4.0-1111.116","5.4.0-1112.117","5.4.0-1113.118"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1","5.15.0-1097.100~20.04.1","5.15.0-1098.101~20.04.1","5.15.0-1099.102~20.04.1","5.15.0-1100.103~20.04.1","5.15.0-1102.105~20.04.1","5.15.0-1103.106~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.1","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1099.105~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1103.109~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1107.113~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1112.118~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1115.121~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44","5.4.0-1044.45","5.4.0-1045.46","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1071.74"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130","5.4.0-1123.131","5.4.0-1124.132","5.4.0-1125.133","5.4.0-1126.134","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1143.152","5.4.0-1144.153","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-174.184~20.04.1","5.15.0-175.185~20.04.1","5.15.0-177.187~20.04.1","5.15.0-178.188~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-183.193~20.04.1","5.15.0-184.194~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-195.205~20.04.1","5.15.0-197.207~20.04.1","5.15.0-198.208~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~20.04.1","5.15.0-1055.55~20.04.1","5.15.0-1057.57~20.04.1","5.15.0-1058.58~20.04.1","5.15.0-1060.60~20.04.1","5.15.0-1061.61~20.04.1","5.15.0-1063.63~20.04.1","5.15.0-1064.66~20.04.1","5.15.0-1065.67~20.04.1","5.15.0-1066.68~20.04.1","5.15.0-1067.69~20.04.1","5.15.0-1068.70~20.04.1","5.15.0-1070.72~20.04.1","5.15.0-1071.73~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1140.150","5.4.0-1141.151","5.4.0-1142.152","5.4.0-1143.153","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1154.164","5.4.0-1155.165","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.171","5.4.0-1162.172","5.4.0-1163.173","5.4.0-1164.174","5.4.0-1165.175"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1102.108~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1116.122~20.04.1","5.15.0-1117.123~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130","5.4.0-1119.131","5.4.0-1120.132","5.4.0-1121.133","5.4.0-1122.134","5.4.0-1129.142","5.4.0-1130.143","5.4.0-1131.144","5.4.0-1132.145","5.4.0-1133.146","5.4.0-1134.147","5.4.0-1135.148","5.4.0-1136.149","5.4.0-1137.150","5.4.0-1139.152","5.4.0-1140.153","5.4.0-1143.156","5.4.0-1144.157","5.4.0-1145.158","5.4.0-1146.159","5.4.0-1147.160","5.4.0-1148.161","5.4.0-1149.162"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1","5.15.0-1097.101~20.04.1","5.15.0-1098.102~20.04.1","5.15.0-1099.103~20.04.1","5.15.0-1100.104~20.04.1","5.15.0-1102.106~20.04.1","5.15.0-1103.107~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.2","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1058.62","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1082.86","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1","5.4.0-1124.134+fips1","5.4.0-1125.135+fips1","5.4.0-1126.136+fips2","5.4.0-1127.137+fips1","5.4.0-1128.138+fips1","5.4.0-1129.139+fips1","5.4.0-1130.140+fips1","5.4.0-1131.141+fips1","5.4.0-1132.142+fips1","5.4.0-1133.143+fips1","5.4.0-1134.144+fips1","5.4.0-1135.145+fips1","5.4.0-1136.146+fips1","5.4.0-1137.147+fips1","5.4.0-1139.149+fips1","5.4.0-1140.151+fips1","5.4.0-1142.153+fips1","5.4.0-1144.155+fips1","5.4.0-1145.156+fips1","5.4.0-1146.156+fips1","5.4.0-1147.157+fips1","5.4.0-1148.158+fips1","5.4.0-1149.159+fips1","5.4.0-1150.160+fips1","5.4.0-1151.161+fips1","5.4.0-1152.162+fips1","5.4.0-1153.163+fips1","5.4.0-1154.164+fips1","5.4.0-1155.165+fips1","5.4.0-1156.166+fips1","5.4.0-1157.167+fips1","5.4.0-1158.168+fips1","5.4.0-1159.169+fips1","5.4.0-1160.170+fips1","5.4.0-1161.172+fips1","5.4.0-1163.174+fips1","5.4.0-1165.176+fips1","5.4.0-1166.177+fips1","5.4.0-1167.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1","5.4.0-1129.136+fips1","5.4.0-1130.137+fips1","5.4.0-1131.138+fips1","5.4.0-1132.139+fips1","5.4.0-1133.140+fips1","5.4.0-1134.141+fips1","5.4.0-1135.142+fips1","5.4.0-1136.143+fips1","5.4.0-1137.144+fips1","5.4.0-1138.145+fips1","5.4.0-1139.146+fips1","5.4.0-1140.147+fips1","5.4.0-1142.149+fips1","5.4.0-1143.150+fips1","5.4.0-1145.152+fips1","5.4.0-1147.154+fips1","5.4.0-1148.156+fips1","5.4.0-1149.157+fips1","5.4.0-1151.158+fips1","5.4.0-1152.159+fips1","5.4.0-1153.160+fips1","5.4.0-1154.161+fips1","5.4.0-1155.162+fips1","5.4.0-1157.164+fips1","5.4.0-1158.165+fips1","5.4.0-1160.166+fips1","5.4.0-1161.167+fips1","5.4.0-1162.168+fips1","5.4.0-1163.169+fips1","5.4.0-1164.170+fips1","5.4.0-1166.172+fips1","5.4.0-1167.173+fips1","5.4.0-1168.174+fips1","5.4.0-1170.176+fips1","5.4.0-1171.177+fips1","5.4.0-1172.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118","5.4.0-1109.119","5.4.0-1110.120","5.4.0-1111.121","5.4.0-1112.122","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1138.148","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1141.151"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1","5.4.0-1128.137+fips1","5.4.0-1129.138+fips1","5.4.0-1130.139+fips1","5.4.0-1131.140+fips1","5.4.0-1132.141+fips1","5.4.0-1133.142+fips1","5.4.0-1134.143+fips1","5.4.0-1135.144+fips1","5.4.0-1136.145+fips1","5.4.0-1137.146+fips1","5.4.0-1138.147+fips1","5.4.0-1139.148+fips1","5.4.0-1140.149+fips1","5.4.0-1141.150+fips1","5.4.0-1142.151+fips1","5.4.0-1143.152+fips1","5.4.0-1145.154+fips1","5.4.0-1146.155+fips1","5.4.0-1147.156+fips1","5.4.0-1148.157+fips1","5.4.0-1149.158+fips1","5.4.0-1150.159+fips1","5.4.0-1151.160+fips1","5.4.0-1152.161+fips1","5.4.0-1153.162+fips1","5.4.0-1154.163+fips1","5.4.0-1155.164+fips1","5.4.0-1156.165+fips1","5.4.0-1157.166+fips1","5.4.0-1159.168+fips1","5.4.0-1160.169+fips1","5.4.0-1161.170+fips1","5.4.0-1162.171+fips1","5.4.0-1163.172+fips1","5.4.0-1164.173+fips1","5.4.0-1165.174+fips1","5.4.0-1166.175+fips1","5.4.0-1167.176+fips1","5.4.0-1168.178+fips1","5.4.0-1169.179+fips1","5.4.0-1170.180+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-176.186","5.15.0-177.187","5.15.0-179.189","5.15.0-181.191","5.15.0-185.195","5.15.0-186.196","5.15.0-187.197","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-198.208","5.15.0-202.212","5.15.0-203.213"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108","5.15.0-1103.110","5.15.0-1104.111","5.15.0-1105.112","5.15.0-1106.113","5.15.0-1108.115","5.15.0-1109.116","5.15.0-1111.118","5.15.0-1112.119","5.15.0-1113.120","5.15.0-1114.121","5.15.0-1115.122","5.15.0-1116.123","5.15.0-1117.124","5.15.0-1119.126","5.15.0-1120.127"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1109.118","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1123.132","5.15.0-1125.134","5.15.0-1126.135"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1","5.15.0-1109.118.1","5.15.0-1110.119.1","5.15.0-1111.120.1","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1120.129","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1124.133","5.15.0-1125.134"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1106.115","5.15.0-1108.117","5.15.0-1109.118","5.15.0-1111.121","5.15.0-1112.122","5.15.0-1114.124","5.15.0-1115.125","5.15.0-1117.127","5.15.0-1118.128","5.15.0-1120.130","5.15.0-1121.131"]},{"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-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1104.110","5.15.0-1105.111","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1115.121","5.15.0-1116.122"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92","5.15.0-1086.94","5.15.0-1087.95","5.15.0-1088.96","5.15.0-1089.97","5.15.0-1091.99","5.15.0-1092.100","5.15.0-1094.102","5.15.0-1095.103","5.15.0-1096.104","5.15.0-1097.105","5.15.0-1098.106","5.15.0-1099.107","5.15.0-1100.108","5.15.0-1102.110","5.15.0-1103.111"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.109","5.15.0-1106.110","5.15.0-1107.111","5.15.0-1108.112","5.15.0-1109.113","5.15.0-1110.114","5.15.0-1111.115","5.15.0-1113.117","5.15.0-1114.118"]},{"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-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1098.104","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1103.109","5.15.0-1104.110","5.15.0-1106.112","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1114.120","5.15.0-1115.121"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","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-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98","5.15.0-1095.100","5.15.0-1096.101","5.15.0-1097.102","5.15.0-1098.103","5.15.0-1100.105","5.15.0-1101.106","5.15.0-1103.108","5.15.0-1104.109","5.15.0-1105.110","5.15.0-1106.111","5.15.0-1107.112","5.15.0-1108.113","5.15.0-1109.114","5.15.0-1111.116","5.15.0-1112.117"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-175.185","5.15.0-177.187","5.15.0-178.188","5.15.0-179.189","5.15.0-181.191","5.15.0-183.193","5.15.0-184.194","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-195.205","5.15.0-197.207","5.15.0-198.208"]},{"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","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97","5.15.0-1098.99","5.15.0-1099.100","5.15.0-1100.101","5.15.0-1101.102","5.15.0-1103.104","5.15.0-1104.105","5.15.0-1106.107","5.15.0-1107.108","5.15.0-1108.109","5.15.0-1109.110","5.15.0-1110.111","5.15.0-1111.112","5.15.0-1112.113","5.15.0-1114.115","5.15.0-1115.116"]},{"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-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1058.58","5.15.0-1060.60","5.15.0-1061.61","5.15.0-1063.63","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1068.70","5.15.0-1070.72","5.15.0-1071.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1054.54","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1059.59"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1103.109","5.15.0-1105.111","5.15.0-1106.112","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1114.120","5.15.0-1116.122","5.15.0-1117.123"]},{"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-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.108","5.15.0-1106.109","5.15.0-1108.111","5.15.0-1110.113"]},{"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:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73","5.15.0-1070.74","5.15.0-1074.78","5.15.0-1075.79","5.15.0-1076.80","5.15.0-1077.81","5.15.0-1078.82","5.15.0-1079.83","5.15.0-1080.84"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1095.97","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1094.96","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106","5.15.0-1105.107","5.15.0-1106.108","5.15.0-1107.109","5.15.0-1108.110","5.15.0-1109.111","5.15.0-1111.115","5.15.0-1112.116"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1107.116","5.15.0-1108.117","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1112.121","5.15.0-1113.122","5.15.0-1114.123","5.15.0-1115.124","5.15.0-1116.125","5.15.0-1118.127","5.15.0-1119.128"]},{"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:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1","5.15.0-1103.110+fips1","5.15.0-1104.111+fips1","5.15.0-1105.112+fips1","5.15.0-1106.113+fips1","5.15.0-1108.115+fips1","5.15.0-1109.116+fips1","5.15.0-1111.118+fips1","5.15.0-1112.119+fips1","5.15.0-1113.120+fips1","5.15.0-1114.121+fips1","5.15.0-1115.122+fips1","5.15.0-1116.123+fips1","5.15.0-1117.124+fips1","5.15.0-1119.126+fips1","5.15.0-1120.127+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1","5.15.0-1109.118+fips1","5.15.0-1110.119+fips1","5.15.0-1111.120+fips1","5.15.0-1114.123+fips1","5.15.0-1116.125+fips1","5.15.0-1117.126+fips1","5.15.0-1118.127+fips1","5.15.0-1119.128+fips1","5.15.0-1121.130+fips1","5.15.0-1122.131+fips1","5.15.0-1123.132+fips1","5.15.0-1125.134+fips1","5.15.0-1126.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1","5.15.0-173.183+fips1","5.15.0-174.184+fips1","5.15.0-176.186+fips1","5.15.0-177.187+fips1","5.15.0-179.189+fips1","5.15.0-181.191+fips1","5.15.0-185.195+fips1","5.15.0-186.196+fips1","5.15.0-190.200+fips1","5.15.0-191.201+fips1","5.15.0-194.204+fips1","5.15.0-198.208+fips1","5.15.0-202.212+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1","5.15.0-1105.114+fips1","5.15.0-1106.115+fips1","5.15.0-1108.117+fips1","5.15.0-1109.118+fips1","5.15.0-1111.121+fips1","5.15.0-1112.122+fips1","5.15.0-1114.124+fips1","5.15.0-1115.125+fips1","5.15.0-1116.126+fips1","5.15.0-1118.128+fips1","5.15.0-1120.130+fips1","5.15.0-1121.131+fips1"]},{"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}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/5b7c23440343e336259cd45017cc901a744c41b0","tags":["web"]},{"url":"https://git.kernel.org/stable/c/460b977a4e71cc319fdadf91c193ec3beaa57263","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/0d46c2565f173bcddcdcaf44a4f69789a20535e2","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/08ef2a82115690d6e229615872ac1731af732497","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/fc59e9482117ebdccd6dc7fa8082f8b980fd021e","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/565bef268d75bf7df665bce6923a88cd0eb74592","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80551","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-p29x-7599-2m4p"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-80551","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80551.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-80551","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0506.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36452","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.45","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.46","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.47","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.48","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.49","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.50","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.51","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.52","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.53","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.54","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.55","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0542.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36453","tags":["report"]},{"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-74715","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-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.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4357","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64567","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80547","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80554","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89711","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89995","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90316","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90329","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-80551","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80551","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-74715","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-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"]}],"sources":{"cve":[{"id":"CVE-2026-80551","title":"s390/vfio_ccw: Ensure first IDAW remains constant","description":"In 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.","status":"published","published":"2026-08-26T14:37:20.554Z","modified":"2026-10-30T12:30:34.924Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"cna"}],"updated_at":"2026-11-02T13:45:36.695039Z"}],"euvd":[{"id":"EUVD-2026-66466","description":"In 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.","status":"published","published":"2026-08-26T14:37:20Z","modified":"2026-10-30T12:30:34Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T16:59:09.83103Z"}],"ghsa":[{"id":"GHSA-p29x-7599-2m4p","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Ensure first...","description":"In 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.","status":"published","published":"2026-08-27T06:31:32Z","modified":"2026-10-30T15:34:17Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:14:49.125638Z"}],"nvd":[{"id":"CVE-2026-80551","description":"In 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.","status":"published","published":"2026-08-26T15:17:09.61Z","modified":"2026-10-30T13:20:06.703Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"secondary"}],"updated_at":"2026-11-02T14:12:41.66469Z"}],"osv":[{"id":"BELL-CVE-2026-80551","status":"published","published":"2026-08-29T06:03:58.575484Z","modified":"2026-11-04T07:16:16.017395339Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-04T07:31:37.974902Z"},{"id":"CVE-2026-80551","title":"s390/vfio_ccw: Ensure first IDAW remains constant","description":"In 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.","status":"published","published":"2026-08-26T14:37:20.554Z","modified":"2026-11-01T02:30:42.932588953Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:45:17.773945Z"},{"id":"DEBIAN-CVE-2026-80551","description":"In the Linux kernel, the following vulnerability has been resolved:  s390/vfio_ccw: Ensure first IDAW remains constant  The first IDAW in a list does not need to be on a 2K/4K boundary like all others, and so is read separately to accurately calculate the size of the buffer needed to read the full IDAL.  Verify that the address found in the first IDAW is unchanged between reads, to ensure a consistent set of IDAWs being worked with.","status":"published","published":"2026-08-26T15:17:09.61Z","modified":"2026-10-31T10:01:50.290526904Z","cvss":[{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:46:04.001673Z"},{"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":"OESA-2026-4357","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\nfs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist\n\nIndex allocation requires at least one bit in the $BITMAP attribute to\ntrack usage of index entries. If the bitmap is empty while index blocks\nare already present, this reflects on-disk corruption.\n\nsyzbot triggered this condition using a malformed NTFS image. During a\nrename() operation involving a long filename (which spans multiple\nindex entries), the empty bitmap allowed the name to be added without\nvalid tracking. Subsequent deletion of the original entry failed with\n-ENOENT, due to unexpected index state.\n\nReject such cases by verifying that the bitmap is not empty when index\nblocks exist.(CVE-2025-40067)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: fix fragment reassembly length accounting\n\nbatman-adv keeps a running payload length for queued fragments and uses it\nto validate a fragment chain before reassembly.\n\nThat accounting currently allows the accumulated fragment length to be\ntruncated during updates. As a result, malformed fragment chains can\nbypass the intended validation and drive reassembly with inconsistent\nlength state, leading to a local denial of service.\n\nFix the accounting by storing the accumulated length in a length-typed\nfield and rejecting update overflows before the existing validation logic\nruns.\n\nThe fix was verified against the original reproducer and against valid\nfragment reassembly paths.(CVE-2026-52914)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix listxattr handling when the buffer is full\n\n[BUG]\nIf an OCFS2 inode has both inline and block-based xattrs, listxattr()\ncan return a size larger than the caller\u0026apos;s buffer when the inline names\nconsume that buffer exactly.\n\nkernel BUG at mm/usercopy.c:102!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nRIP: 0010:usercopy_abort+0xb7/0xd0 mm/usercopy.c:102\nCall Trace:\n __check_heap_object+0xe3/0x120 mm/slub.c:8243\n check_heap_object mm/usercopy.c:196 [inline]\n __check_object_size mm/usercopy.c:250 [inline]\n __check_object_size+0x5c5/0x780 mm/usercopy.c:215\n check_object_size include/linux/ucopysize.h:22 [inline]\n check_copy_size include/linux/ucopysize.h:59 [inline]\n copy_to_user include/linux/uaccess.h:219 [inline]\n listxattr+0xb0/0x170 fs/xattr.c:926\n filename_listxattr fs/xattr.c:958 [inline]\n path_listxattrat+0x137/0x320 fs/xattr.c:988\n __do_sys_listxattr fs/xattr.c:1001 [inline]\n __se_sys_listxattr fs/xattr.c:998 [inline]\n __x64_sys_listxattr+0x7f/0xd0 fs/xattr.c:998\n ...\n\n[CAUSE]\nCommit 936b8834366e (\u0026quot;ocfs2: Refactor xattr list and remove\nocfs2_xattr_handler().\u0026quot;) replaced the old per-handler list accounting\nwith ocfs2_xattr_list_entry(), but it kept using size == 0 to detect\nprobe mode.\n\nThat assumption stops being true once ocfs2_listxattr() finishes the\ninline-xattr pass. If the inline names fill the caller buffer exactly,\nthe block-xattr pass runs with a non-NULL buffer and a remaining size of\nzero. ocfs2_xattr_list_entry() then skips the bounds check, keeps\ncounting block names, and returns a positive size larger than the\nsupplied buffer.\n\n[FIX]\nDetect probe mode by testing whether the destination buffer pointer is\nNULL instead of whether the remaining size is zero.\n\nThat restores the pre-refactor behavior and matches the OCFS2 getxattr\nhelpers. Once the remaining buffer reaches zero while more names are\nleft, the block-xattr pass now returns -ERANGE instead of reporting a\nsize larger than the allocated list buffer.(CVE-2026-53041)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Use krealloc_array() in dal_vector_reserve()\n\n[Why \u0026amp; How]\ndal_vector_reserve() computes the allocation size as\n\u0026quot;capacity * vector-\u0026gt;struct_size\u0026quot; using uint32_t arithmetic, which can\nsilently wrap to a small value on overflow. This would cause krealloc to\nreturn a smaller buffer than expected, leading to heap overflows on\nsubsequent vector appends.\n\nReplace krealloc() with krealloc_array() which performs an internal\noverflow check and returns NULL on wrap, preventing the issue.\n\n(cherry picked from commit 37668568641ccc4cc1dbca4923d0a16609dd5707)(CVE-2026-53329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nexfat: fix potential use-after-free in exfat_find_dir_entry()\n\nIn exfat_find_dir_entry(), the buffer_head obtained from\nexfat_get_dentry() is released with brelse(bh) before the fall-through\nTYPE_EXTEND branch reads the directory entry through ep (which points\ninto bh-\u0026gt;b_data):\n\n\tbrelse(bh);\n\tif (entry_type == TYPE_EXTEND) {\n\t\t...\n\t\tlen = exfat_extract_uni_name(ep, entry_uniname);\n\t\t...\n\t}\n\nAfter brelse() drops our reference, nothing guarantees that the\nunderlying page backing bh-\u0026gt;b_data remains valid for the subsequent\nexfat_extract_uni_name() read. This is the same pattern fixed in\ncommit fc961522ddbd (\u0026quot;exfat: Fix potential use after free in\nexfat_load_upcase_table()\u0026quot;).\n\nMove brelse(bh) so it runs after ep is no longer dereferenced on\neach branch.\n\nConfirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y\n+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image\n(long filename with same-hash collisions forcing the TYPE_EXTEND path).\nWith a debug-only invalidate_bdev() inserted between brelse(bh) and\nthe ep read to make the stale-deref window deterministic, the\nunpatched kernel faults:\n\n  BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0\n  BUG: unable to handle page fault for address: ffff88801a5fa0c2\n  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0\n\nWith this patch applied, the same instrumented harness completes\ncleanly under the same sanitizer stack. I have not reproduced a\ncrash on an uninstrumented kernel under ordinary reclaim; the\ninstrumented A/B establishes the lifetime violation and that the\npatch closes it, not an unaided triggerability claim.(CVE-2026-63808)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: tp_meter: restrict number of unacked list entries\n\nWhen the unacked_list is unbound, an attacker could send messages with\nsmall lengths and appropriated seqno + gaps to force the receiver to\nallocate more and more unacked_list entries. And the end either causing an\nout-of-memory situation or increase the management overhead for the (large)\nlist that significant portions of CPU cycles are wasted in searching\nthrough the list.\n\nWhen limiting the list to a specific number, it is important to still\ncorrectly add a new entry to the list. But if the list became larger than\nthe limit, the last entry of the list (with the highest seqno) must be\ndropped to still allow the earlier seqnos to finish and therefore to\ncontinue the process. Otherwise, the process might get stuck with too high\nseqnos which are not handled by batadv_tp_ack_unordered().(CVE-2026-63834)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: v: prevent OGM aggregation on disabled hardif\n\nWhen an interface gets disabled, the worker is correctly disabled by\nbatadv_hardif_disable_interface() -\u0026gt; ... -\u0026gt; batadv_v_ogm_iface_disable().\nIn this process, the skb aggr_list is also freed.\n\nBut batadv_v_ogm_send_meshif() can still queue new skbs (via\nbatadv_v_ogm_queue_on_if()) to the aggr_list. This will only stop after all\ncores can no longer find the RCU protected list of hard interfaces. These\nqueued skbs will never be freed or consumed by batadv_v_ogm_aggr_work.\n\nThe batadv_v_ogm_iface_disable() function must block\nbatadv_v_ogm_queue_on_if() to avoid leak of skbs.(CVE-2026-63835)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niio: gyro: itg3200: fix i2c read into the wrong stack location\n\nitg3200_read_all_channels() takes `__be16 *buf\u0026apos; as a parameter and\nfills the i2c_msg destination as `(char *)\u0026amp;buf\u0026apos;. Since `buf\u0026apos; is the\nparameter (a pointer), `\u0026amp;buf\u0026apos; is the address of the local pointer\nslot on the stack of itg3200_read_all_channels(), not the address\nof the caller\u0026apos;s scan buffer. The (char *) cast hides the type\nmismatch.\n\ni2c_transfer() therefore writes ITG3200_SCAN_ELEMENTS * sizeof(s16)\n= 8 bytes into the parameter\u0026apos;s stack slot, which is discarded when\nthe function returns. The caller\u0026apos;s scan buffer in\nitg3200_trigger_handler() is never written to, so\niio_push_to_buffers_with_timestamp() pushes uninitialised stack\ncontents to userspace via /dev/iio:deviceX every scan -- both a\nfunctional bug (no actual gyroscope or temperature data is\ndelivered through the triggered buffer) and an information leak.\n\nThe non-buffered read_raw() path is unaffected: it goes through\nitg3200_read_reg_s16() which uses `\u0026amp;out\u0026apos; on a local s16 value,\nwhere that is correct.\n\nDrop the spurious `\u0026amp;\u0026apos; so the i2c read writes into the caller\u0026apos;s\nbuffer.(CVE-2026-63934)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: team: fix NULL pointer dereference in team_xmit during mode change\n\n__team_change_mode() clears team-\u0026gt;ops with memset() before restoring\nsafe dummy handlers via team_adjust_ops(). A concurrent team_xmit()\nrunning under RCU on another CPU can read team-\u0026gt;ops.transmit during\nthis window and call a NULL function pointer, crashing the kernel.\n\nThe race requires a mode change (CAP_NET_ADMIN) concurrent with\ntransmit on the team device.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000000\n Oops: 0010 [#1] SMP KASAN NOPTI\n RIP: 0010:0x0\n Call Trace:\n  team_xmit (drivers/net/team/team_core.c:1853)\n  dev_hard_start_xmit (net/core/dev.c:3904)\n  __dev_queue_xmit (net/core/dev.c:4871)\n  packet_sendmsg (net/packet/af_packet.c:3109)\n  __sys_sendto (net/socket.c:2265)\n\nThe original code assumed that no ports means no traffic, so mode\nchanges could freely memset()/memcpy() the ops.  AF_PACKET with\nforced carrier breaks that assumption.\n\nPrevent the race instead of making it safe: replace memset()/memcpy()\nwith per-field updates that never touch transmit or receive.  Those\ntwo handlers are managed solely by team_adjust_ops(), which already\ninstalls dummies when tx_en_port_count == 0 (always true during mode\nchange since no ports are present).  WRITE_ONCE/READ_ONCE prevent\nstore/load tearing on the handler pointers.\n\nsynchronize_net() before exit_op() drains in-flight readers that may\nstill reference old mode state from before port removal switched the\nhandlers to dummies.(CVE-2026-64190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: reject free space cache with more entries than pages\n\nWhen loading a v1 free space cache, __load_free_space_cache() takes\nnum_entries and num_bitmaps straight from the on-disk\nbtrfs_free_space_header. That header is stored in the tree_root under a key\nwith type 0, which the tree-checker has no case for, so neither count is\nvalidated before the load trusts it.\n\nThe load loops num_entries times and maps the next page whenever the current\none runs out, going through io_ctl_check_crc() -\u0026gt; io_ctl_map_page(), which\ndoes io_ctl-\u0026gt;pages[io_ctl-\u0026gt;index++]. But pages[] is allocated in\nio_ctl_init() from the cache inode\u0026apos;s i_size, not from num_entries:\n\n\tnum_pages = DIV_ROUND_UP(i_size_read(inode), PAGE_SIZE);\n\tio_ctl-\u0026gt;pages = kcalloc(num_pages, sizeof(struct page *), GFP_NOFS);\n\nSo if num_entries claims more records than the pages can hold, io_ctl-\u0026gt;index\nruns off the end of pages[]. The write side never hits this because\nio_ctl_add_entry() and io_ctl_add_bitmap() both stop once\nio_ctl-\u0026gt;index \u0026gt;= io_ctl-\u0026gt;num_pages; the read side just never had the same\ncheck.\n\nTo trigger it, take a clean cache (num_entries = \u0026lt;N\u0026gt; here), set num_entries\nin the header to 0x10000, and fix up the leaf checksum so it still passes\nthe tree-checker. The cache inode has i_size = 65536, so num_pages is 16 and\npages[] is a 16-pointer (kmalloc-128) array. The load now tries to read\n65536 entries, io_ctl-\u0026gt;index walks up to 16, and pages[16] is read past the\narray:\n\n  BUG: KASAN: slab-out-of-bounds in io_ctl_check_crc (fs/btrfs/free-space-cache.c:420 fs/btrfs/free-space-cache.c:565)\n  Read of size 8 at addr ffff88800c833a80 by task kworker/u8:3/58\n   io_ctl_check_crc (fs/btrfs/free-space-cache.c:420 fs/btrfs/free-space-cache.c:565)\n   __load_free_space_cache (fs/btrfs/free-space-cache.c:655 fs/btrfs/free-space-cache.c:820)\n   load_free_space_cache (fs/btrfs/free-space-cache.c:1017)\n   caching_thread (fs/btrfs/block-group.c:880)\n   btrfs_work_helper (fs/btrfs/async-thread.c:312)\n   process_one_work\n   worker_thread\n   kthread\n   ret_from_fork\n\nfree-space-cache.c:420 is io_ctl_map_page(), inlined into io_ctl_check_crc()\nat line 565, which is why that is the frame KASAN names. The out-of-bounds\nslot is then treated as a struct page and handed to crc32c(), so the bad\nread turns into a GP fault.\n\nAdd the missing check to io_ctl_check_crc(), which is where both the entry\nloop and the bitmap loop end up. When num_entries is too large the load now\nfails like any corrupt cache: __load_free_space_cache() drops it and rebuilds\nthe free space from the extent tree, so a valid cache is never rejected.(CVE-2026-64567)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: wacom: stop hardware after post-start probe failures\n\nwacom_parse_and_register() starts HID hardware before registering inputs\nand initializing pad LEDs/remotes. Those later steps can fail, but their\nerror paths currently release Wacom resources without stopping the HID\nhardware.\n\nRoute post-hid_hw_start() failures through hid_hw_stop() before\nreleasing driver resources.\n\nThis issue was identified during our ongoing static-analysis research while\nreviewing kernel code.(CVE-2026-68091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: make release_scratchbuffers idempotent\n\nbrcmf_pcie_release_scratchbuffers() frees the shared.scratch and\nshared.ringupd DMA buffers with dma_free_coherent() but does not clear\nthe pointers afterwards, unlike the sibling release_ringbuffers() which\nNULLs commonrings/flowrings/idxbuf on release.\n\nBoth the bus_reset .reset callback (brcmf_pcie_reset) and\nbrcmf_pcie_remove() call release_scratchbuffers.  When reset teardown\nhas run before removal, remove\u0026apos;s own teardown would call\ndma_free_coherent() a second time on the already-freed DMA allocation.\n\nNULL the pointers after free, matching release_ringbuffers(), so a later\nrelease observes that the allocation has already been released.  This\npatch makes repeated sequential release safe; the reset-work lifetime is\nhandled separately by the following patch.\n\nThis issue was found by an in-house static analysis tool.(CVE-2026-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid()\n\nThe vm pointer returned from amdgpu_vm_get_vm_from_pasid() is only\nvalid while the lock is still being held. Once xa_unlock_irqrestore is\ncalled and returned, the pointer is no longer under lock and is subject\nto modification. Since, the caller still dereferences vm-\u0026gt;task_info in\namdgpu_vm_get_task_info_vm() after the lock is removed, this causes a\nuse after unlock problem.\n\nRemove the lifetime issue present in amdgpu_vm_get_task_info_pasid()\nthrough removing the amdgpu_vm_get_vm_from_pasid() function from\namdgpu_vm.c and making the relevant code inline to hold the lock while\nit is still in use.\n\n(cherry picked from commit 9d01579f3f868b333acc901815972685989092c7)(CVE-2026-68245)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: cancel sched scan results work on unregister\n\ncfg80211_sched_scan_results() can queue rdev-\u0026gt;sched_scan_res_wk from a\ndriver result notification while a scheduled scan request is present. The\nwork callback recovers the containing cfg80211_registered_device and then\nlocks the wiphy and walks the scheduled-scan request list.\n\nwiphy_unregister() already makes the wiphy unreachable and drains rdev work\nitems before cfg80211_dev_free() can release the object, but it does not\ndrain sched_scan_res_wk. A queued or running result work item can therefore\ncross the unregister/free boundary and access freed rdev state.\n\nThe buggy scenario involves two paths, with each column showing the order\nwithin that path:\n\nscheduled-scan result path:        unregister/free path:\n1. cfg80211_sched_scan_results()   1. interface teardown stops and\n   queues rdev-\u0026gt;sched_scan_res_wk.    removes the scheduled scan request.\n2. cfg80211_wq starts the work     2. wiphy_unregister() drains other\n   item and recovers rdev.            rdev work items.\n3. The worker locks rdev-\u0026gt;wiphy    3. cfg80211_dev_free() destroys and\n   and walks rdev state.              frees rdev.\n\nCancel sched_scan_res_wk in wiphy_unregister() alongside the other rdev\nwork items. cancel_work_sync() removes a pending result notification and\nwaits for an already running callback, so cfg80211_dev_free() cannot free\nrdev while this work item is still active.\n\nValidation reproduced this kernel report:\nBUG: KASAN: use-after-free in cfg80211_sched_scan_results_wk+0x4a6/0x530\nWorkqueue: cfg80211 cfg80211_sched_scan_results_wk [cfg80211]\nRead of size 8\nCall trace:\n  dump_stack_lvl+0x66/0xa0\n  print_report+0xce/0x630\n  cfg80211_sched_scan_results_wk+0x4a6/0x530\n  srso_alias_return_thunk+0x5/0xfbef5\n  __virt_addr_valid+0x224/0x430\n  kasan_report+0xac/0xe0\n  lockdep_hardirqs_on_prepare+0xea/0x1a0\n  process_one_work+0x8d0/0x18f0 (kernel/workqueue.c:3212)\n  lock_is_held_type+0x8f/0x100\n  worker_thread+0x5ad/0xfd0\n  __kthread_parkme+0xc6/0x200\n  kthread+0x31e/0x410\n  trace_hardirqs_on+0x1a/0x170\n  ret_from_fork+0x576/0x810\n  __switch_to+0x57e/0xe20\n  __switch_to_asm+0x33/0x70\n  ret_from_fork_asm+0x1a/0x30(CVE-2026-68414)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rt2x00: avoid full teardown before work setup in probe\n\nrt2x00lib_probe_dev() uses the full rt2x00lib_remove_dev() teardown for\nall probe failures. However, drv_data allocation and workqueue allocation\ncan fail before intf_work, autowakeup_work and sleep_work have been\ninitialized.\n\nDo not enter the full remove path until the probe has reached the point\nwhere those work items are set up. Return directly for drv_data allocation\nfailure, and use a small early cleanup path for workqueue allocation\nfailure.\n\nThis issue was found by our static analysis tool and then confirmed by\nmanual review of rt2x00lib_probe_dev() and rt2x00lib_remove_dev(). The\nearly probe exits should not call a common teardown path that assumes the\nlater work setup has already completed.\n\nA QEMU PoC forced alloc_ordered_workqueue() to fail before the work\ninitializers are reached. The resulting fail path entered\nrt2x00lib_remove_dev(), and DEBUG_OBJECTS reported invalid work drains with\nrt2x00lib_probe_dev() and rt2x00lib_remove_dev() in the stack.(CVE-2026-72005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath9k: fix OOB access from firmware tx status queue ID\n\nath_tx_edma_tasklet() accesses sc-\u0026gt;tx.txq[ts.qid] where ts.qid is a\n4-bit hardware field (0-15), but the txq array only has\nATH9K_NUM_TX_QUEUES (10) entries. A qid \u0026gt;= 10 causes an OOB array\naccess.\n\nAdd a bounds check on ts.qid before using it as an array index.(CVE-2026-74408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/radeon: fix integer overflow in radeon_align_pitch()\n\nradeon_align_pitch() has the same kind of overflow issue as the old\namdgpu helper: both the alignment round-up add and the final\n\u0026apos;aligned * cpp\u0026apos; calculation can overflow signed int.\n\nIf that wraps, radeon_mode_dumb_create() can end up returning an\ninvalid pitch or creating a zero-sized dumb buffer.\n\nFix this by using check_add_overflow() for the alignment round-up and\ncheck_mul_overflow() for the final pitch calculation, returning 0 on\noverflow. Also reject zero pitch and size in\nradeon_mode_dumb_create().\n\nFound via AST-based call-graph analysis using sqry.(CVE-2026-74417)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: clear new_transport when removing a peer\n\nsctp_process_asconf_param() stores a newly added peer transport in\nasoc-\u0026gt;new_transport. After all parameters in the ASCONF chunk have been\nprocessed, sctp_sf_do_asconf() uses this pointer to send a HEARTBEAT to the\nnew transport.\n\nAn authenticated ASCONF from a remote SCTP peer can add a transport and\nremove it again with a wildcard DEL-IP parameter in the same chunk. The\nwildcard deletion preserves the transport on which the ASCONF arrived, but\nremoves the newly added transport through\nsctp_assoc_del_nonprimary_peers(). The removal does not clear\nasoc-\u0026gt;new_transport, leaving it pointing to the removed transport.\n\nsctp_sf_do_asconf() then creates a HEARTBEAT whose chunk-\u0026gt;transport points\nto the removed transport without holding a transport reference. During\nlocal address replacement, src_out_of_asoc_ok keeps this HEARTBEAT on\ncontrol_chunk_list. After the transport is freed by RCU, a successful\nASCONF_ACK for the replacement address releases the queued HEARTBEAT and\nsctp_outq_select_transport() reads the freed transport\u0026apos;s state.\n\nThe issue was found during a static audit of SCTP objects. With an\nauthenticated peer, the reproducer triggered the same KASAN report in 2\nof 2 unpatched runs on a KASAN-enabled netdev/main kernel:\n\n  BUG: KASAN: slab-use-after-free in sctp_outq_select_transport\n  Read of size 4 at addr ffff88800b9bd95c by task python3/197\n\n  Call Trace:\n   sctp_outq_select_transport+0x549/0x8b0 [sctp]\n   sctp_outq_flush+0x306/0x2c60 [sctp]\n   sctp_transport_immediate_rtx+0xaf/0x260 [sctp]\n   sctp_process_asconf_ack+0xa48/0xf70 [sctp]\n\n  Allocated by task 197:\n   sctp_transport_new+0x68/0x650 [sctp]\n   sctp_assoc_add_peer+0x258/0x12a0 [sctp]\n   sctp_process_asconf+0x5e9/0x1090 [sctp]\n\n  Last potentially related work creation:\n   __call_rcu_common.constprop.0+0x77/0xb70\n   sctp_assoc_del_nonprimary_peers+0x7c/0xd0 [sctp]\n   sctp_process_asconf+0xd9c/0x1090 [sctp]\n\nThe first invalid access was a four-byte read of transport-\u0026gt;state at\nnet/sctp/outqueue.c:833. The same reproducer completed the full\nauthenticated ASCONF and local-address replacement sequence with this\nchange without a KASAN report or oops.\n\nClear new_transport when its peer is removed, before it can be used to\ncreate the HEARTBEAT.(CVE-2026-74586)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/psi: Shut down rtpoll_timer in psi_cgroup_free()\n\npsi_schedule_rtpoll_work() is called locklessly from the scheduler hotpath\nand can race psi_trigger_destroy() taking down the last rtpoll trigger under\nrtpoll_trigger_lock:\n\n  psi_schedule_rtpoll_work()        psi_trigger_destroy()\n\n  rcu_read_lock();\n  task = rcu_dereference(rtpoll_task);\n                                    rcu_assign_pointer(rtpoll_task, NULL);\n                                    timer_delete(\u0026amp;rtpoll_timer);\n  mod_timer(\u0026amp;rtpoll_timer, ...);\n  rcu_read_unlock();\n                                    synchronize_rcu();\n                                    kthread_stop(task_to_destroy);\n\nThe group can then be freed with the re-armed timer still pending, and\npoll_timer_fn() runs on freed memory.\n\n461daba06bdc (\u0026quot;psi: eliminate kthread_worker from psi trigger scheduling\nmechanism\u0026quot;) deleted the timer synchronously after the synchronize_rcu(),\nwhich prevented this but raced trigger creation instead: the deletion could\ncancel the timer that a new trigger set armed during the grace period and,\nas creation also reinitialized the timer at the time, corrupt it.\n8f91efd870ea (\u0026quot;psi: Fix race between psi_trigger_create/destroy\u0026quot;) moved the\ninitialization into group_init() and the deletion into the locked section,\ntrading the creation races for the window above.\n\nNeither placement in the destruction path works. A pending timer firing\nwhile the group is alive is harmless though. poll_timer_fn() just wakes the\nrtpoll waitqueue and doesn\u0026apos;t re-arm itself. Bind the timer to the group\u0026apos;s\nlifetime instead and shut it down in psi_cgroup_free(). Nothing can arm it\nby then. timer_shutdown_sync() because the timer is never armed again.(CVE-2026-74594)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntipc: read le-\u0026gt;link under the node lock in tipc_node_link_down()\n\ntipc_node_link_down() caches the link pointer before taking n-\u0026gt;lock:\n\n\tstruct tipc_link *l = le-\u0026gt;link;\t\t/* unlocked */\n\n\tif (!l)\n\t\treturn;\n\ttipc_node_write_lock(n);\n\tif (!tipc_link_is_establishing(l)) {\t/* deref l */\n\t...\n\t\ttipc_link_reset(l);\t\t/* write into l */\n\tif (delete) {\n\t\tkfree(l);\n\t\tle-\u0026gt;link = NULL;\n\nThe delete=true caller frees that very object under n-\u0026gt;lock, so the lock\ndoes not protect the cached pointer against it:\n\n - CPU A, delete=false: tipc_rcv() on TIPC_LINK_DOWN_EVT, or the link\n   supervision timer via tipc_node_timeout(), reads l unlocked and then\n   dereferences it under n-\u0026gt;lock;\n - CPU B, delete=true: netlink TIPC_NL_BEARER_DISABLE -\u0026gt; bearer_disable()\n   -\u0026gt; tipc_node_delete_links() -\u0026gt; tipc_node_link_down(n, bearer_id, true)\n   -\u0026gt; kfree(l).\n\nThe link is freed with plain kfree(), not kfree_rcu(), and for UDP bearers\ndisable_media() only schedules the asynchronous cleanup_bearer() work, so\nits synchronize_net() runs after the links are already gone.  An in-flight\nCPU A that has read l therefore dereferences freed memory once B frees it:\na use-after-free read in tipc_link_is_establishing(), and a use-after-free\nwrite via tipc_link_reset() on the establishing branch.\n\nThe following trace was captured on 7.2.0-rc5-00284-gaf39eb111ce6:\n\n  BUG: KASAN: slab-use-after-free in tipc_link_is_establishing (net/tipc/link.c:285)\n  Read of size 4 at addr ffff88802e2aa068 by task swapper/2/0\n   tipc_link_is_establishing (net/tipc/link.c:285)\n   tipc_node_link_down (net/tipc/node.c:1076)\n   tipc_node_timeout (net/tipc/node.c:843)\n  Allocated by task 9549:\n   tipc_link_create (net/tipc/link.c:490)\n   tipc_node_check_dest (net/tipc/node.c:1279)\n   tipc_disc_rcv (net/tipc/discover.c:252)\n   tipc_udp_recv (net/tipc/udp_media.c:389)\n  Freed by task 9549:\n   tipc_node_link_down (net/tipc/node.c:1084)\n   tipc_node_delete_links (net/tipc/node.c:1320)\n   bearer_disable (net/tipc/bearer.c:414)\n   __tipc_nl_bearer_disable (net/tipc/bearer.c:992)\n\nMove the le-\u0026gt;link read inside tipc_node_write_lock(), so it is serialised\nagainst the kfree() in the delete path.  A racing teardown now either has\nnot run yet, and we see a valid link, or has already run, and we see NULL.(CVE-2026-74609)\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\nsctp: clear control chunk transport if it is being removed\n\nsctp_make_heartbeat_ack() caches the destination transport in\nchunk-\u0026gt;transport without taking a reference. When src_out_of_asoc_ok is\nenabled, the HEARTBEAT ACK may remain queued on control_chunk_list instead\nof being transmitted immediately.\n\nIf the peer transport is removed while the chunk is still queued,\nsctp_assoc_rm_peer() drops the transport and schedules it for RCU freeing,\nbut only clears cached transport pointers in out_chunk_list.  The queued\ncontrol chunk therefore retains a dangling transport pointer.\n\nOnce an ASCONF_ACK clears the suppression and the queued control chunk is\ntransmitted, SCTP dereferences the stale transport pointer, leading to a\nuse-after-free.\n\nFix this by also clearing chunk-\u0026gt;transport for queued control chunks in\ncontrol_chunk_list when removing the transport.(CVE-2026-74688)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Implement a crw lock\n\nUnlike the channel_program struct, which covers synchronous I/O\nsubmissions and asynchronous interrupts, the CRW region relies\nexclusively on asynchronous events coming from hardware.\n\nImplement a lock to manage the list of those payloads, to ensure\nthey are read cohesively.(CVE-2026-80547)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Selectively expand io_mutex\n\nThe io_mutex was defined to serialize the io_regions, but then has\nalso sort of been associated with the I/O themselves because of\nthe close relationship they share.\n\nWith the handful of races that are possible, the choices are either to:\n A) expand the scope of io_mutex to close these remaining windows, or\n B) reduce the scope of io_mutex to just io_region, and introduce a new\n    lock mechanism for the remaining I/O resources\n\nThis patch implements A, since B brings with it a lot more interactions\nthat would need to be tracked and kept in a correct hierarchy. It also\ntakes advantage of the workqueue element for cp_free() that now gets\ncalled out of fsm_notoper(), which could be invoked out of an interrupt\ncontext and thus cannot acquire a mutex itself.(CVE-2026-80548)\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\ns390/vfio_ccw: Limit the number of channel program segments\n\nThe processing of channel programs, and the CCWs within them, is done\nrecursively. As such, there is an arbitrary (but not architectural)\nlimit to the number of CCWs that can exist in a single channel program.\n\nThe vfio-ccw logic breaks these channel programs into segments whenever\nit encounters a Transfer-In-Channel (TIC) CCW, and the combined number\nof segments count towards the global limit. Impose an equivalent limit\nto the number of segments until such logic can be made non-recursive.(CVE-2026-80554)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: synaptics-rmi4 - fix F55 transmitter electrode count typo\n\nDuring F55 sensor detection, the transmitter (TX) electrode count was\nincorrectly assigned the value of the receiver (RX) electrode count\ndue to copy-paste typos.\n\nThis incorrect value was then propagated to the driver data and used\nby F54 to determine the diagnostics report size. On devices with more\nRX than TX electrodes, this inflated the perceived TX count, leading\nto incorrect report size calculations and potential out-of-bounds\nbuffer accesses.\n\nFix the typos by correctly assigning the TX electrode counts.(CVE-2026-80754)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfs: validate attr entry pointer before field access\n\nxfs_attr3_leaf_verify_entry() accesses lentry/rentry fields (namelen,\nvaluelen) before checking if the entry pointer itself is within bounds.\nIf nameidx is crafted to point near the end of the buffer, these field\naccesses can read out-of-bounds before the bounds check at\nname_end \u0026gt; buf_end is performed.\n\nAdd explicit bounds checks for entry pointers before accessing their\nfields. Use offsetof() to check that the start of the flexible array\nmember (nameval/name) is within bounds, which ensures all preceding\nfields are safe to access.(CVE-2026-80805)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: don\u0026apos;t enable DAX on new encrypted files\n\nCurrently, when a new encrypted regular file is created, the call to\next4_set_inode_flags(inode, init=true) in __ext4_new_inode() is made\nbefore EXT4_INODE_ENCRYPT is set.  As a result, it can set S_DAX if the\nfilesystem is mounted with \u0026quot;-o dax=always\u0026quot;.\n\nEXT4_INODE_ENCRYPT then actually gets set a bit later in\n__ext4_new_inode(), when it calls fscrypt_set_context() which calls\next4_set_context().  ext4_set_context() sets EXT4_INODE_ENCRYPT and\ncalls ext4_set_inode_flags(inode, init=false) to set S_ENCRYPTED too.\n\nThis was intended to clear S_DAX as well.  However, this was broken by\ncommit 043546e46dc7 (\u0026quot;fs/ext4: Only change S_DAX on inode load\u0026quot;).  This\ncauses data written to the file to bypass encryption, also causing\nxfstests failures such as generic/548 (when \u0026quot;-o dax=always\u0026quot; is used).\n\nFix this by simplifying the flow by making __ext4_new_inode() set\nEXT4_INODE_ENCRYPT earlier.  This makes it take effect in\next4_set_inode_flags(inode, init=true), making S_DAX never be set.\n\nSimilarly, make EXT4_STATE_MAY_INLINE_DATA never be set in the first\nplace on new encrypted inodes.  Then it doesn\u0026apos;t need to be cleared.\n\nAs a result of these simplifications, ext4_set_context() no longer needs\nto change inode flags or state when \u0026apos;handle != NULL\u0026apos;.  Remove that too.(CVE-2026-80806)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: f_tcm: keep port count until LUN teardown completes\n\ntcm_usbg_drop_nexus() permits session removal once tpg_port_count\nreaches zero. However, usbg_port_unlink() currently decrements that\ncount from the fabric_pre_unlink() callback, before core_dev_del_lun()\nwaits for active se_lun references to drain.\n\nIf removal of the last LUN races a nexus removal, the latter can observe\na zero port count and call target_remove_session(). This frees\nsess_cmd_map while an in-flight struct usbg_cmd, including its work item,\ncan still be accessed.\n\nOverlapping the last-LUN unlink with nexus removal reproduces this\nlifetime violation as a DEBUG_OBJECTS \u0026quot;free active\u0026quot; warning for\nusbg_cmd_work, followed by a target-core BUG/Oops.\n\nThe generic target-core unlink path has no callback after\ncore_dev_del_lun() completes. Add an optional fabric_post_unlink()\ncallback and use it for the f_tcm port count. The count now remains\nnonzero until core_dev_del_lun() has finished draining active LUN\nreferences, preventing nexus removal from freeing the session during\ncommand completion.(CVE-2026-80854)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: vsie: zero stale crypto bits\n\nWhen shadowing crypto access bits from a format0 apcb (crycb 0 or 1),\nthe bits 64..255 are unchanged from whatever is in the vsie page in the\ncrycb and thus in the apcb. This gives a nested guest potential access\nto a device no longer available. Zero out the remaining bits.(CVE-2026-80921)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: do not dereference an unset send buffer on the SMC-D teardown path\n\nsmc_close_stream_wait() calls smc_tx_prepared_sends() from inside its\nsk_wait_event() condition, and sk_wait_event() evaluates that condition\nonce with the socket lock released. smcd_buf_detach() clears\nconn-\u0026gt;sndbuf_desc from smc_conn_kill() under lock_sock(), so a link group\nterminating while a socket waits there leaves the helper dereferencing\nNULL, faulting out of close(). SIOCOUTQ reads the field by hand, and\nsmc_close_cancel_work() drops the lock across two cancel_*_sync() calls.\n\nSample the pointer once in the helper, report nothing prepared while it is\nunset, and bound the ioctl the same way. The receive tasklet dereferences\nthe field directly in smc_cdc_msg_recv_action(), not through this helper;\n1/2 is what keeps it from running that late.(CVE-2026-80984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: thunderbolt: Mark the connection down when bringing it up fails\n\nEvery failure path in tbnet_connected_work() undoes its own work and\nreturns without clearing login_sent, so the connection still looks\nestablished. The next tbnet_tear_down() therefore takes its main branch\nand repeats a teardown that already happened: it stops rings that are\nalready stopped, which is a dev_WARN() and fatal under panic_on_warn,\nand it releases net-\u0026gt;remote_transmit_path even on the HopID mismatch\npath, where this connection never owned that id, silently freeing one\nthat someone else is still using.\n\nClear login_sent on those paths. That is enough for tbnet_tear_down() to\nleave the unwound state alone, and login_received has to stay set: it\nrecords that the peer has logged in and carries the transmit path it gave\nus, which nothing on this side can make the peer send again. Two things\nchange beyond keeping the teardown out of the way: the logout request in\nthat block is no longer sent, and the peer\u0026apos;s next login request now\nre-queues our login work rather than connected_work, giving the\nconnection a fresh login instead of a retry on stale state.(CVE-2026-80989)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix flow mask use-after-free on flow deletion\n\nThe commit in the Fixes tag below made so flow-\u0026gt;mask free is scheduled\nvia RCU right after it is removed from the flow table.  The pointer\nstays in the flow structure and it can be accessible while in the same\nRCU critical section.  This is done to avoid requiring ovs_mutex for\nthe ovs_flow_free().\n\nHowever, while removing the flow during processing of CMD_DEL, we do\nnot take RCU read lock before the removal, and ovs_flow_cmd_fill_info()\nuses the flow-\u0026gt;mask pointer afterwards.  The RCU read lock is taken,\nbut it\u0026apos;s already late at that point.  The comment on that line\nacknowledges that the lock is cosmetic and doesn\u0026apos;t serve a real purpose.\n\nThis leads to use-after-free if the RCU grace period passes between\nremoval and the filling.  It is a short race window, but it is there\nand can lead to a real crash in case memory allocation for the info\ntakes a bit longer:\n\n BUG: KASAN: slab-use-after-free in __ovs_nla_put_key\n             net/openvswitch/flow_netlink.c:1996\n BUG: KASAN: slab-use-after-free in ovs_nla_put_key+0x2463/0x2e30\n             net/openvswitch/flow_netlink.c:2250\n Read of size 4 at addr ffff88801ee89970 by task ovs_flow_del_ec/9487\n\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __ovs_nla_put_key net/openvswitch/flow_netlink.c:1996\n  ovs_nla_put_key+0x2463/0x2e30 net/openvswitch/flow_netlink.c:2250\n  ovs_flow_cmd_fill_info+0x420/0x9c0 net/openvswitch/datapath.c:930\n  ovs_flow_cmd_del+0x53a/0x970 net/openvswitch/datapath.c:1467\n  ...\n  netlink_rcv_skb+0x156/0x420 net/netlink/af_netlink.c:2556\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 9487:\n  mask_alloc net/openvswitch/flow_table.c:967\n  flow_mask_insert net/openvswitch/flow_table.c:1012\n  ovs_flow_tbl_insert+0xea2/0x1a90 net/openvswitch/flow_table.c:1084\n  ovs_flow_cmd_new+0x7e3/0xd90 net/openvswitch/datapath.c:1086\n  ...\n  netlink_rcv_skb+0x156/0x420 net/netlink/af_netlink.c:2556\n\n Freed by task 9485:\n  rcu_free_sheaf+0x1e/0x100 mm/slub.c:5978\n  rcu_do_batch kernel/rcu/tree.c:2645\n  rcu_core+0x59c/0x10c0 kernel/rcu/tree.c:2897\n  handle_softirqs+0x1e4/0x9a0 kernel/softirq.c:622\n  ...\n  instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1062\n\novs_flow_tbl_remove() must be called after the ovs_flow_cmd_fill_info()\nto avoid this race.  This also helps with cleaning up the forced cast\nand the cosmetic RCU read lock.  Before the commit in the Fixes tag the\norder did not matter as long as the flow object itself was not freed.\n\nA wider RCU critical section could be another option, but we have a\nGFP_KERNEL allocation in the way.\n\nReported by Trend Micro\u0026apos;s Zero Day Initiative as ZDI-CAN-32042.(CVE-2026-80994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmmc: via-sdmmc: stop card-detect handling on probe failure\n\nrequest_irq() registers the SD card-detect interrupt and the probe enables\nit before mmc_add_host() runs. If mmc_add_host() fails, the error path only\nunmaps the registers and returns: the interrupt stays registered, so the\nhandler keeps running against the host once it is freed. via_sdc_isr()\ndereferences sdhost and its MMIO base and schedules carddet_work, which\nvia_sdc_card_detect() also runs against freed memory through its\ncontainer_of() dereference.\n\nAdd a probe-error path that disables and frees the interrupt and cancels\ncarddet_work before unmapping. carddet_work can re-enable the device\ninterrupt via via_reset_pcictrl(), which restores PCIINTCTRL, so mask it\nagain after cancelling the work.\n\nThis issue was found by an in-house static analysis tool and confirmed by\nmanual code review.(CVE-2026-89440)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix NULL deref on untransmitted RECONF completion\n\nsctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out() and\nsctp_process_strreset_resp() complete a pending stream reconfiguration\nrequest by stopping the reconf timer on the transport it was sent on:\n\n\tt = asoc-\u0026gt;strreset_chunk-\u0026gt;transport;\n\tif (timer_delete(\u0026amp;t-\u0026gt;reconf_timer))\n\t\tsctp_transport_put(t);\n\nchunk-\u0026gt;transport is assigned by __sctp_packet_append_chunk() when the\nchunk is appended to an outbound packet, and sctp_outq_flush_ctrl() arms\nthe reconf timer at that same point. A request already published in\nasoc-\u0026gt;strreset_chunk but not yet transmitted has neither, so completing\nit dereferences NULL.\n\nTwo ways to get there. sctp_send_asconf_del_ip() sets\nasoc-\u0026gt;src_out_of_asoc_ok without sending anything when the address being\nremoved is the association\u0026apos;s last one, and sctp_outq_flush_ctrl() then\nleaves every non-ASCONF control chunk queued; as only\nsctp_process_asconf_ack() clears that flag, it persists. An unprivileged\nprocess that removes such an address and then asks for a stream reset\npanics the kernel from softirq. A peer needs neither ASCONF nor local\nhelp: sctp_cmd_interpreter() uncorks the outqueue only once the whole\npacket has been processed, so a reply built while walking a RECONF chunk\nstays untransmitted for the rest of that walk, and one RECONF chunk\ncarrying [Incoming SSN Reset Request, Outgoing SSN Reset Request,\nResponse] -- or two RECONF chunks in one packet -- reaches the same\ndereference.\n\n  KASAN: null-ptr-deref in range [0x00000000000001e8-0x00000000000001ef]\n  RIP: 0010:timer_delete+0x67/0x110\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   sctp_process_strreset_addstrm_out (net/sctp/stream.c:832)\n   sctp_sf_do_reconf (net/sctp/sm_statefuns.c:4212)\n   sctp_do_sm (net/sctp/sm_sideeffect.c:1172)\n   sctp_assoc_bh_rcv (net/sctp/associola.c:1044)\n   sctp_rcv (net/sctp/input.c:243)\n   ip_local_deliver (net/ipv4/ip_input.c:262)\n   process_backlog (net/core/dev.c:6680)\n   \u0026lt;/IRQ\u0026gt;\n\nA response can only acknowledge a request that was actually sent, so do\nnot match asoc-\u0026gt;strreset_chunk while chunk-\u0026gt;transport is NULL. Guarding\nthe lookup covers all three completion sites.(CVE-2026-89477)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: reject a read that transferred too few bytes\n\nnvme_tcp_recv_data() completes a request once the current C2HData PDU\nhas been consumed. Nothing compares the total bytes received against\nthe length the command asked for: struct nvme_tcp_request has no\nreceive-side counter, queue-\u0026gt;data_remaining is per queue, and\nblk_mq_end_request() completes for blk_rq_bytes(rq) unconditionally\nwith no residual concept anywhere above.\n\nA controller can therefore answer a 4096-byte read with 512 bytes and\nhave it reported as a complete read; user space then gets 4096 bytes of\nwhich 3584 are whatever was already in the page. I reproduced that with\na test target.\n\nCount the bytes received and refuse to complete a successful read whose\ncount does not match, at the two NVME_TCP_F_DATA_SUCCESS paths and in\nnvme_tcp_process_nvme_cqe(). The success test shifts req-\u0026gt;status right\nby one, because the driver keeps the wire value there and shifts it on\ncompletion, so the check must see what the completion path will see.\nOnly REQ_OP_READ is checked, because there the length comes from the\nsectors the request covers; a passthrough command is built by its\nsubmitter, which picks both command and buffer, so the kernel has\nnothing to compare against.(CVE-2026-89480)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix host memory disclosure on R2T for a read command\n\nnvme_tcp_handle_r2t() does not check the direction of the request the\nR2T refers to. A malicious controller can send an R2T for a READ and\nthe host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the\nH2CData header and nvme_tcp_try_send_data() sends the request\u0026apos;s data\nbuffer. That buffer is the READ destination, so its contents go to the\ncontroller.\n\nThe command then completes normally and nothing is logged.\n\nAgainst a test controller that answers every READ with an R2T, a 4096\nbyte buffered read returned all 4096 bytes, split over two R2Ts. The\npages contained stale kernel data, including an array of struct page\npointers.\n\nReject an R2T for a request that is not a write.(CVE-2026-89481)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlockd: pin next file across nlm_inspect_file lock-drop\n\nnlm_traverse_files() pins the current file with f_count++ across\na mutex_unlock for nlm_inspect_file(), but nothing pins the saved\nnext pointer.  A concurrent nlm_release_file() can kfree the next\nfile during the unlock window, and the iterator dereferences freed\nmemory on the next loop step.\n\nPin both current and next before the lock-drop.  Advance by\nswapping the pinned cursors at the end of each iteration so next\nis always held alive across the unlock.\n\nAlways call nlm_file_release() after dropping the iteration pin,\nregardless of whether the file matched the predicate.  Use\nnlm_file_inuse(), which does a live walk of the inode lock list,\nrather than the cached f_locks field, so skipped files that never\nran nlm_inspect_file() are evaluated correctly.\n\nBecause every file in a hash bucket is now pinned and released,\nfiles skipped by the is_failover_file predicate that have no\nlocks, blocks, shares, or external references are deleted during\ntraversal.  The old code never evaluated skipped files for\ncleanup.  The new behavior is intentional: such files are stale\nand should not persist in the table.(CVE-2026-89485)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: only skb_tx_error() a packet we are about to drop\n\nqueue_userspace_packet() borrows the packet skb -- it only copies it into\na private netlink message (user_skb) and does not own it; on return\ndo_execute_actions() keeps forwarding it through the flow\u0026apos;s remaining\nactions. Its error path nevertheless calls skb_tx_error(skb), which via\nskb_zcopy_clear() does skb_shinfo(skb)-\u0026gt;flags \u0026amp;= ~SKBFL_ALL_ZEROCOPY,\nstripping SKBFL_SHARED_FRAG from that live skb (skb_tx_error()\u0026apos;s kerneldoc\nsays \u0026quot;skb must be freed afterwards\u0026quot;).\n\nFor a MSG_ZEROCOPY skb carrying page-cache frags, SKBFL_SHARED_FRAG is\nwhat makes esp_input() skb_cow_data() before in-place AEAD; once it is\nstripped a later local ESP-in-UDP delivery decrypts in place over pages\nthe sender does not own -- an unprivileged page-cache write (the\n\u0026quot;Fragnesia\u0026quot; primitive).\ndo_execute_actions() ignores output_userspace()\u0026apos;s return value, so any\naction after a failed USERSPACE upcall inherits the stripped skb.\n\nMove the skb_tx_error() to the flow-miss drop path - the \u0026quot;default\u0026quot;\nbranch of ovs_dp_process_packet()\u0026apos;s switch(error), before kfree_skb().\n\nThe call has been here since commit 36d5fe6a0007 (\u0026quot;core, nfqueue,\nopenvswitch: Orphan frags in skb_zerocopy and handle errors\u0026quot;) but was\nharmless until esp_input() began relying on SKBFL_SHARED_FRAG to gate\nin-place decrypt; only then did stripping it on a still-forwarded skb\nbecome a page-cache write primitive.(CVE-2026-89487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate directory-index entry counts when reading metadata\n\nocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and\nsignature of an indexed-directory block before it reaches higher-level\ncallers, but neither validator bounds the ocfs2_dx_entry_list counts\nagainst the capacity of the block that holds them.\n\nocfs2_dx_dir_search() then walks\n\n\tfor (i = 0; i \u0026lt; le16_to_cpu(entry_list-\u0026gt;de_num_used); i++)\n\t\tdx_entry = \u0026amp;entry_list-\u0026gt;de_entries[i];\n\nover de_num_used entries with no bounds check.  entry_list is either\ndx_leaf-\u0026gt;dl_list (from ocfs2_read_dx_leaf) or, for an inline root,\ndx_root-\u0026gt;dr_entries.  A crafted on-disk image can set de_num_used (and\nde_count, which is the __counted_by_le() bound of de_entries) to 0xffff\nand make the walk read far past the end of the 4KB metadata block, giving\na slab out-of-bounds read reachable from any path lookup, stat() or open()\non an indexed directory once the image is mounted.\n\nCommit 775c17386a6f (\u0026quot;ocfs2: validate dx_root extent list fields during\nblock read\u0026quot;) already bounds dr_list for the non-inline dx_root, but left\nthe inline dr_entries path and the dx_leaf dl_list unchecked.  Add the\nsame read-time validation for both entry lists: de_count must equal the\ncapacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and\nde_num_used must not exceed de_count, rejecting corrupted metadata with\n-EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry\narray.\n\nde_count is always written as exactly the block capacity when a leaf or\ninline root is formatted, so the equality check does not reject any valid\nimage.\n\nFound by 0sec automated security-research tooling (https://0sec.ai).(CVE-2026-89492)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nqede: Fix NULL pointer dereference in TPA fragment processing\n\nUnder memory pressure, the qede driver encounters NULL pointer\ndereferences when processing TPA continuation fragments.\n\nCommit 8a8633978b84 (\u0026quot;qede: Add build_skb() support.\u0026quot;) accidentally\ndropped the assignment of tpa_info-\u0026gt;buffer.data in qede_tpa_start().\n\nWhen memory pressure causes an SKB allocation failure in qede_tpa_start(),\nthe driver sets tpa_start_fail = true and attempts to recycle the physical\npage later in qede_tpa_end() via qede_reuse_page(). However, because\nbuffer.data was left uninitialized (NULL), qede_reuse_page() pushes a\n\u0026quot;ghost\u0026quot; BD (valid DMA mapping but NULL data pointer) back into the\nactive Rx ring.\n\nThe next time the hardware uses this ring slot, it passes a NULL page\nto qede_fill_frag_skb(), causing a kernel panic.\n\nExample crash from production system:\n BUG: unable to handle kernel NULL pointer dereference at 0x8\n RIP: qede_fill_frag_skb+0x96/0x430 [qede]\n Call Trace:\n   qede_rx_int+0xb06/0x1de0\n   qede_poll+0x2f4/0x6c0\n   __napi_poll+0x2d/0x130\n\nFix the root cause by restoring the tpa_info-\u0026gt;buffer.data assignment\nin qede_tpa_start(), ensuring valid pages are correctly tracked and\nrecycled. Additionally, update the stale comment for\nstruct qede_agg_info::buffer to reflect its current usage.(CVE-2026-89511)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\naudit: avoid dropping live tree ref on fsnotify rule autoremove\n\naudit_del_rule() is used for both netlink deletion templates and internal\nfsnotify autoremove.  The former passes a parsed template which owns a\ntemporary tree reference; the latter passes the installed entry itself.\n\nThe unconditional audit_put_tree() at the end of audit_del_rule() assumes\nthe template case.  For mixed AUDIT_DIR plus AUDIT_EXE rules, an fsnotify\nautoremove event therefore drops the installed rule\u0026apos;s live tree reference.\nRepeating this across rules sharing the same tree can free the tree while\nanother rule still references it, and a later autoremove dereferences the\nfreed pathname while comparing rules.\n\nMove the temporary-tree put to audit_rule_change(), the caller that owns\ndeletion templates.  Keep it in the AUDIT_DEL_RULE cleanup so both\nsuccessful deletion and -ENOENT still release the parser-owned tree.\n\n[PM: dropped unnecessary comment for line length reasons](CVE-2026-89643)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: revoke copy-notify stateids before dropping their reference\n\nCopy-notify stateids live in the s2s_cp_stateids IDR and on their parent\nstid\u0026apos;s sc_cp_list, pinned by a single membership reference.\n_free_cpntf_state_locked() only unlinks an entry once its refcount reaches\nzero, so any revoke path that runs while a concurrent\nfind_cpntf_state()/manage_cpntf_state() holder has elevated cs_count drops\nthe reference without unlinking, leaving the entry discoverable with its\nmembership reference already consumed. A second revoke or a laundromat tick\nthen frees it while the reader still holds the pointer -- a\nKASAN-detectable use-after-free at the reader\u0026apos;s nfs4_put_cpntf_state().\n\nThis affected all three revoke paths:\n\n  - The parent-stid drain (nfs4_free_cpntf_statelist()) repeatedly called\n    _free_cpntf_state_locked() on the first list entry; a holder that had\n    bumped cs_count made it return early, so the next iteration\n    re-decremented and burned the holder\u0026apos;s reference.\n\n  - OFFLOAD_CANCEL (manage_cpntf_state()) and laundromat expiry likewise\n    used _free_cpntf_state_locked() and could drop 2-\u0026gt;1 without unlinking.\n\nAdd revoke_cpntf_state_locked(), which unhashes the entry from the IDR and\nsc_cp_list first (deferring the final free to any holder), and use it from\nall three revoke paths. The drain now walks with list_for_each_entry_safe()\nand revokes each entry unconditionally, so it terminates in one pass per\nentry regardless of cs_count. The unhash is gated on\n!list_empty(\u0026amp;cps-\u0026gt;cp_list); the idr_remove() gate matters because\nidr_alloc_cyclic() may have recycled the so_id by then. Keep\n_free_cpntf_state_locked() for the reference-holder put path only, where a\nconcurrent revoke may already have unlinked the entry (its list_del_init()\nthen a no-op).(CVE-2026-89663)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: gate nfs2 setacl by argp-\u0026gt;mask\n\nThe NFSACL v2 SETACL path shares the decoder convention used by its\nv3 sibling: nfsaclsvc_decode_setaclargs() fills in argp-\u0026gt;acl_access\nonly when NFS_ACL is set in the request mask and argp-\u0026gt;acl_default\nonly when NFS_DFACL is set, leaving the other pointer NULL because\nthe argument buffer is zeroed up to pc_argzero before decode.\n\nnfsacld_proc_setacl() then hands both pointers to set_posix_acl()\nunconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS\n\u0026quot;remove this ACL type\u0026quot; operation, so an omitted arm is\nindistinguishable from an explicit request to delete that ACL. A\nSETACL carrying only NFS_ACL silently strips the directory\u0026apos;s default\nACL; mask=0 strips both.\n\nThis is the same defect just fixed in nfsd3_proc_setacl(); apply the\nsame remedy. Gate each set_posix_acl() call on its mask bit and\ninitialize error to 0 so that a request with neither bit set leaves\nthe on-disk ACLs untouched and returns success. The out_drop_lock\npath and the unconditional posix_acl_release() in\nnfsaclsvc_release_setacl() already tolerate the skipped arms.(CVE-2026-89672)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: fix stale s2s_cp_stateids IDR entry for async COPY\n\nFor an async COPY, nfsd4_copy() called nfs4_init_copy_state() before\ndup_copy_fields(), so the s2s_cp_stateids IDR was pointed at\n\u0026amp;u-\u0026gt;copy-\u0026gt;cp_stateid -- memory in the per-rqstp COMPOUND buffer that is\nreused by the next request. dup_copy_fields() copies only the value into\nasync_copy, so the IDR slot dangled at the transient buffer for the whole\nbackground copy. Any IDR walker then dereferences reused request memory:\nthe laundromat reads cs_type from it and, if the bytes look like an\nexpired NFS4_COPYNOTIFY_STID, follows into\nrefcount_dec()/idr_remove()/kfree() on garbage; manage_cpntf_state() has\nthe same exposure via idr_find().\n\nDuplicate the fields first, then register the stateid on the stable\nasync_copy. result-\u0026gt;cb_stateid is unchanged.(CVE-2026-89676)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: validate symlink target length in NFSv4 CREATE\n\nnfsd4_decode_create() accepts an unbounded cr_datalen from the wire for\nNF4LNK symlink targets, allowing a client to force a kmalloc of up to\nthe maximum RPC payload size (several MiB) per COMPOUND op that persists\nuntil compound teardown.  The VFS rejects oversized targets with\nENAMETOOLONG, but the allocation has already occurred.\n\nReject cr_datalen == 0 early with nfserr_inval and cr_datalen greater\nthan NFS4_MAXPATHLEN (PATH_MAX) with nfserr_nametoolong to bound the\nallocation.(CVE-2026-89699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check\n\nThe header for commit e75b23f9e323 (\u0026quot;nfsd: check d_can_lookup in\nfh_verify of directories\u0026quot;) details the assumption that justified\nadding the WARN_ON_ONCE to nfsd_mode_check(), that assumption is\ninvalid (in the case of NFS reexport).\n\nWhen NFSD exports an NFS filesystem it is very possible for\nnfsd_mode_check() to encounter a @dentry that doesn\u0026apos;t have\ni_op-\u0026gt;lookup (see nfs_fhget()\u0026apos;s NFS_ATTR_FATTR_MOUNTPOINT and\nNFS_ATTR_FATTR_V4_REFERRAL handling, and d_flags_for_inode()).\n\nSo remove nfsd_mode_check()\u0026apos;s WARN_ON_ONCE(). The nfserr_notdir\nreturn on that branch must stay. It guards the subsequent\nlookup_one_unlocked() -\u0026gt; __lookup_slow() path, which calls\ninode-\u0026gt;i_op-\u0026gt;lookup() with no NULL check, so returning nfserr_notdir\nis what keeps a client LOOKUP into such a @dentry from dereferencing\na NULL method pointer.(CVE-2026-89711)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: check truncate permission under inode lock\n\nnfsd_setattr() checks whether a size update needs NFSD_MAY_TRUNC\nbefore it takes inode_lock(). The comparison uses the file size sampled\nby that unlocked read, but the actual ATTR_SIZE update is applied later\nunder inode_lock() by notify_change().\n\nThis leaves a TOCTOU window for append-only files. If a client sends a\nSETATTR that does not shrink the file at the time of the unlocked\nsample, a concurrent append can extend the file before nfsd_setattr()\ntakes inode_lock(). notify_change() then applies a real truncation\nwithout the NFSD_MAY_TRUNC check that rejects IS_APPEND(inode). The VFS\ntruncate syscall paths perform their own append-only checks before\ncalling notify_change(), so NFSD must make this decision against the\nlocked size it is about to change.\n\nSplit the write-count acquisition from the truncation permission check.\nKeep get_write_access() before the locked setattr work, then recheck\nwhether the requested size is below i_size_read(inode) after inode_lock()\nhas been acquired and before notify_change(ATTR_SIZE). This also avoids\nthe plain unlocked inode-\u0026gt;i_size load.(CVE-2026-89713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature\n\nsensor_hub_get_feature() clamps its return value to the caller\u0026apos;s buffer\nsize, but the copy loop still copies field-\u0026gt;report_size / 8 bytes for\neach report value. A malicious HID descriptor can advertise a large\nfeature field size while an IIO caller supplies a small stack buffer,\nsuch as a single s32, causing an out-of-bounds write.\n\nHID core stores parsed report values in __s32 slots and clamps extracted\nvalues to 32 bits. Reject feature fields that require more than one slot\nper value, guard the total byte count calculation, and clamp each\nper-value copy to the remaining caller buffer.(CVE-2026-89729)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: fix user path of nested backing files\n\nbacking_file_open() derives the path to be stored in the new backing\nfile from user_file-\u0026gt;f_path.  This is incorrect when user_file itself\nis a backing file, which is the case for nested stacking filesystems,\ne.g. overlayfs mounts where the lowerdir of one overlayfs is the merged\ndirectory of another.  Since commit def3ae83da02 (\u0026quot;fs: store real path\ninstead of fake path in backing file f_path\u0026quot;) the f_path of a backing\nfile holds the real path of the intermediate layer, not the path that\nthe user opened.\n\nCommit 924577e4f6ca (\u0026quot;ovl: Fix nested backing file paths\u0026quot;) fixed this\nfor such configurations by passing file_user_path() from\novl_open_realfile().  However, commit 6af36aeb147a (\u0026quot;lsm: add\nbacking_file LSM hooks\u0026quot;) changed the first argument of\nbacking_file_open() from the user path back to the user file and\nderived the path from user_file-\u0026gt;f_path again, silently re-introducing\nthe problem.\n\nAs a result, files mapped through a nested overlayfs show the wrong\npath in /proc/\u0026lt;pid\u0026gt;/maps and in perf/ftrace mmap records.  For example,\nwith two nested overlayfs mounts:\n\n  mkdir -p /ovl/{lower,upper,work,merged} /ovl/nested\n  echo hello \u0026gt; /ovl/lower/foo\n  mount -t overlay overlay \\\n\t-o lowerdir=/ovl/lower,upperdir=/ovl/upper,workdir=/ovl/work \\\n\t/ovl/merged\n  # at least two lowerdirs are needed when upperdir is nonexistent\n  mount -t overlay overlay \\\n\t-o lowerdir=/ovl/merged:/ovl/lower /ovl/nested\n\nmapping /ovl/nested/foo shows a disconnected path instead of the user\npath:\n\n  # readlink /proc/self/fd/3\n  /ovl/nested/foo\n  # grep foo /proc/self/maps\n  7f6e2c100000-7f6e2c101000 r--s 00000000 00:24 15813027 /foo\n\nThe bogus path is derived from the f_path of the intermediate backing\nfile, whose mount is a private clone that d_path() cannot resolve.\n\nFix this by using file_user_path(), which returns the outermost\nuser-visible path for backing files and falls back to\n\u0026amp;user_file-\u0026gt;f_path for regular files.  This restores the behavior of\ncommit 924577e4f6ca (\u0026quot;ovl: Fix nested backing file paths\u0026quot;) for\noverlayfs and also fixes the same problem for the other\nbacking_file_open() callers, fuse passthrough and erofs ishare, when\ntheir user file is itself a backing file.\n\nbacking_tmpfile_open() has the same pattern but is not affected: it is\nonly called by ovl_create_tmpfile() for the upper layer, and another\noverlayfs is rejected as upperdir by the DCACHE_OP_REAL check in\novl_mount_dir_check(), so its user_file can never be a backing file.(CVE-2026-89768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisofs: fix out-of-bounds page array access on empty zisofs block\n\nzisofs_uncompress_block()\u0026apos;s empty-block fast path returns\npcount \u0026lt;\u0026lt; PAGE_SHIFT, ignoring the incoming poffset, unlike the\ndecompression path which returns bytes produced relative to poffset.\nzisofs_fill_pages() uses that return to advance its page cursor, so when\nthe zisofs block size is below PAGE_SIZE and a sub-page block leaves\npoffset partway into a page, a following empty block over-counts and\nadvances pages[] one element past its end, after which\n\u0026quot;if (poffset \u0026amp;\u0026amp; *pages)\u0026quot; reads pages[1] out of bounds.  rock.c only\nrejects a block-size shift \u0026gt; 17, so a crafted \u0026quot;ZF\u0026quot; Rock Ridge record can\nset it below PAGE_SHIFT; the bug is reached by an ordinary read() of a\ncompressed file on such a mounted ISO9660 image.\n\nReturn the byte count relative to poffset and zero only\n[poffset, PAGE_SIZE) of the first page, matching the decompression path.\nThe page-aligned case (poffset == 0) is unaffected.\n\n  BUG: KASAN: slab-out-of-bounds in zisofs_read_folio (fs/isofs/compress.c:290)\n  Read of size 8 at addr ffff88800f5eac48 by task exploit/142\n   zisofs_read_folio (fs/isofs/compress.c:290)\n   read_pages (mm/readahead.c:184)\n   ...\n   filemap_read (mm/filemap.c:2814)\n   vfs_read (fs/read_write.c:574)\n   __x64_sys_pread64 (fs/read_write.c:769)\n   do_syscall_64 (arch/x86/entry/syscall_64.c:94)\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)\n  The buggy address is located 0 bytes to the right of the\n  allocated 8-byte region in the kmalloc-8 cache(CVE-2026-89778)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm: fix race between partial drm_dev_register() failure and ioctl\n\nIf drm_dev_register() fails after registering a minor (e.g. render minor\nregistered, primary minor fails), userspace could have opened the first\nminor and entered a drm_dev_enter() critical section. Since the\nunplugged flag was never set, the ioctl proceeds while the error path\ntears down device resources.\n\nFix this by introducing drm_dev_synchronize_unplug(), which sets the\nunplugged flag and waits for the SRCU barrier, ensuring all in-flight\ndrm_dev_enter() critical sections complete before cleanup proceeds; call\nit on the error path of drm_dev_register().(CVE-2026-89823)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix cs84xx use-after-free on host teardown\n\nqla84xx_put_chip() drops the last reference to ha-\u0026gt;cs84xx and frees it via\n__qla84xx_chip_release() without clearing ha-\u0026gt;cs84xx. During teardown it ran\nbefore scsi_remove_host(), which is what removes the 84xx_fw_version host\nsysfs attribute. A concurrent read of that attribute in the window between\nthe two calls executes qla24xx_84xx_fw_version_show(), which dereferences\nthe freed ha-\u0026gt;cs84xx, resulting in a use-after-free.\n\nMove qla84xx_put_chip() to after scsi_remove_host() in both\nqla2x00_remove_one() and qla2x00_disable_board_on_pci_error(). Once\nscsi_remove_host() returns, the sysfs attribute is gone and kernfs has\ndrained any in-flight show(), so no reader can touch cs84xx; the put still\nruns before the host and ha are freed.(CVE-2026-89854)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation\n\nha-\u0026gt;msix_count is u16, but ha-\u0026gt;max_req_queues, ha-\u0026gt;max_rsp_queues and\nha-\u0026gt;max_qpairs are u8. Deriving the queue count as\n\u0026quot;ha-\u0026gt;max_req_queues = ha-\u0026gt;msix_count - 1\u0026quot; therefore truncates: a board\n(or a misconfigured/malicious hot-plugged device) advertising 257 MSI-X\nvectors yields msix_count - 1 == 256, which truncates to 0. An MSI-X\ncount of 1 zeroes it as well, and in target mode the subsequent\n\u0026quot;ha-\u0026gt;max_req_queues--\u0026quot; then underflows 0 to 255.\n\nWhen the count is 0, qla2x00_alloc_queues() calls\nkzalloc_objs(struct req_que *, 0), which returns ZERO_SIZE_PTR. That is\nnot NULL, so the allocation check passes and the following\n\u0026quot;ha-\u0026gt;req_q_map[0] = req\u0026quot; dereferences ZERO_SIZE_PTR, corrupting memory\nor crashing the kernel.\n\nAdd qla_calc_queue_count() to clamp the derived value into\n[1, QLA_MAX_QUEUES - 1] so it always fits in u8 and is never zero, and\nuse it at all three derivation sites (qla25xx_iospace_config(),\nqla83xx_iospace_config() and qla24xx_enable_msix()). Also guard the\ntarget-mode decrement so it cannot reintroduce a zero (which would in\nturn underflow max_qpairs).(CVE-2026-89856)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()\n\nIn the format 1 path, the virtual port is located on ha-\u0026gt;vp_list while\nholding vport_slock, but the lock is dropped before vp is used:\nqla_update_host_map() is called and VP_IDX_ACQUIRED/REGISTER_FC4_NEEDED/\nREGISTER_FDMI_NEEDED are set on vp. No reference is taken across that\nwindow, so a concurrent qla24xx_deallocate_vp_id() can tear the vport\ndown and free it, leading to a use-after-free.\n\nTake a vport reference (vref_count) under vport_slock when the matching\nvp is found, and drop it after the last use of\nvp. qla24xx_deallocate_vp_id() waits for vref_count to reach zero before\nunlinking and freeing the vport, so the pointer stays valid. This\nmatches the reference idiom already used by the other ha-\u0026gt;vp_list\ntraversals.(CVE-2026-89861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: Fix memory corruption by not reinjecting CK machine checks\n\nChannel-subsystem damage machine checks are for the host channel\nsubsystem. The guest channel subsystem is emulated in the userspace VMM.\nThere is no point in forwarding such machine checks into the guest.\n\nThis also simplifies the machine check reinjection and avoids kfree of a\nstack variable as reported by sashiko.  There might be still machine\nchecks that have the ck bit set with another bit (like instruction\ndamage), mask out the CK bit in s390_backup_mcck_info(), like the CP and\nED bits already are.(CVE-2026-89920)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: hyper-v: Clamp stimer deadline to avoid livelock\n\nFix an issue where userspace or the guest can program an Hyper-V\nsynthetic timer to have a deadline in the past via integer overflow,\npreventing the CPU from making progress and triggering an RCU stall.\n\nHyper-V\u0026apos;s SynIC exposes 4 per-vCPU synthetic timers to the\nguest, which are emulated by KVM. Each is programmed through the\nHV_X64_MSR_STIMERi_CONFIG and HV_X64_MSR_STIMERi_COUNT MSRs. Depending\non CONFIG, COUNT represents either the absolute expiration time or the\nperiod of a periodic timer, both expressed in 100ns ticks. These timers\nmay be set both by the guest (WRMSR) and the host (KVM_SET_MSRS).\n\nWhen the timer is enabled, stimer_start() translates COUNT to an\nabsolute monotonic deadline and arms an hrtimer. If COUNT is set to a\nvalue close to U64_MAX, the deadline calculation can overflow.\n\n    ktime_add_ns(ktime_now, 100 * (stimer-\u0026gt;exp_time - time_now))\n\nThis can result in a CPU livelock. stimer_start() arms the timer\nvia hrtimer_start() with a deadline in the past, which causes it to\nimmediately fire. The stimer callback then raises KVM_RQ_HV_STIMER, with\nthe intention of causing KVM to deliver a synthetic interrupt on the\nnext vCPU guest enter.\n\nThen, once userspace issues KVM_RUN, vcpu_enter_guest() consumes the\nrequest, calling kvm_hv_process_stimers(). This would normally disable\nthe timer via stimer_expiration() once the deadline is in the past.\nHowever, the deadline comparison is done between the KVM reference\ncounter and stime-\u0026gt;exp_time, which is a big value close to U64_MAX, so\nthis never happens for a few thousand years.\n\nkvm_hv_process_timers() then re-arms the timer via stimer_start(), since\nit was not disabled, which again fires immediately. Before entering\nthe guest, kvm_vcpu_exit_request() checks kvm_request_pending(),\nwhich returns true due to the newly raised KVM_REQ_HV_STIMER. Then\nvcpu_enter_guest() aborts the guest entry, returning early into\nvcpu_run(), which loops back again into vcpu_enter_guest(), restarting\nthe cycle.\n\nSince there are no manual yields in this loop, a task with SCHED_FIFO\nmay starve RCU grace-period kthreads, which exposes the stalls found\nby syzcaller:\n\n    rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:\n    rcu:    (detected by 1, t=10502 jiffies, g=14269, q=1142 ncpus=2)\n    rcu: All QSes seen, last rcu_preempt kthread activity 10500 (4294965239-4294954739), jiffies_till_next_fqs=1, root -\u0026gt;qsmask 0x0\n    rcu: rcu_preempt kthread starved for 10500 jiffies! g14269 f0x2 RCU_GP_WAIT_FQS(5) -\u0026gt;state=0x0 -\u0026gt;cpu=0\n    rcu:    Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.\n        ( ... )\n    Call Trace:\n     \u0026lt;IRQ\u0026gt;\n     __run_hrtimer kernel/time/hrtimer.c:1773 [inline]\n     __hrtimer_run_queues+0x408/0xc30 kernel/time/hrtimer.c:1841\n     hrtimer_interrupt+0x45b/0xaa0 kernel/time/hrtimer.c:1903\n     local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1045 [inline]\n     __sysvec_apic_timer_interrupt+0x102/0x3e0 arch/x86/kernel/apic/apic.c:1062\n     instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1056 [inline]\n     sysvec_apic_timer_interrupt+0xa1/0xc0 arch/x86/kernel/apic/apic.c:1056\n     \u0026lt;/IRQ\u0026gt;\n     \u0026lt;TASK\u0026gt;\n     asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:697\n    RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]\n    RIP: 0010:_raw_spin_unlock_irqrestore+0xa8/0x110 kernel/locking/spinlock.c:194\n    Code: 74 05 e8 0b f4 5f f6 48 c7 44 24 20 00 00 00 00 9c 8f 44 24 20 f6 44 24 21 02 75 4f f7 c3 00 02 00 00 74 01 fb bf 01 00 00 00 \u0026lt;e8\u0026gt; 23 6b 27 f6 65 8b 05 7c 60 5a 07 85 c0 74 40 48 c7 04 24 0e 36\n    RSP: 0018:ffffc900040a7320 EFLAGS: 00000206\n    RAX: 5de15cb931505900 RBX: 0000000000000a06 RCX: 5de15cb931505900\n    RDX: 0000000000000007 RSI: ffffffff8daa9dc3 RDI: 0000000000000001\n    RBP: ffffc900040a73b0 R08: ffffffff8fc3d0\n---truncated---(CVE-2026-89927)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nVMX: Always flush vpid02 on first use\n\nMake sure vpid02 is always flushed on first use by setting last_vpid=0\nwhen allocating vpid02.  nested_vmx_transition_tlb_flush() will always\ndetect a VPID change on first VM-Enter after VMXON, because VPID=0 in\nvmcs12 is not allowed if L1 enables VPID.\n\nThis avoids using stale TLB entries from a previous lifetime of the\nVPID, that might have been associated with a different vCPU (or a\ncompletely different VM).\n\nNote that last_vpid is already being initialized as 0 when the vCPU is\ncreated, but it is not reset when vpid02 is freed on VMXOFF. Hence, the\nproblem can only occur if L1 does VMXOFF -\u0026gt; VMXON, runs an L2, and KVM\nhappens to reuse a VPID that has TLB entries on the physical CPU.(CVE-2026-89932)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm/btt: reject an arena whose nfree is below the lane count\n\nThe BTT info block\u0026apos;s nfree field, the number of reserve free blocks, is\nread from the medium without validation.  btt_freelist_init() and\nbtt_rtt_init() size the per-lane freelist[] and rtt[] arrays by nfree,\nbut the I/O path indexes them by the lane from nd_region_acquire_lane(),\nwhich is bounded by nd_region-\u0026gt;num_lanes (ND_MAX_LANES), not by nfree.\nA crafted or foreign arena whose nfree is below the lane count makes\nfreelist[lane]/rtt[lane] run past the allocation: an out-of-bounds write.\n\nbtt.rst documents the nlanes = min(nfree, num_cpus) invariant, which the\ncode does not currently honor: num_lanes is ND_MAX_LANES regardless of\nnfree.  Reject an arena whose nfree is below num_lanes at discovery,\nbefore the per-lane arrays are allocated, enforcing that invariant.(CVE-2026-89965)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: check the data direction of a C2HData PDU\n\nnvme_tcp_handle_c2h_data() finds the request by command id and checks\nthat it has a payload, but it does not check that the command asked for\ndata to be read.  A controller that answers a write command with C2HData\ntherefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits\nWARN_ON_ONCE(i-\u0026gt;data_source) and returns 0.  The receive path turns that\ninto -EFAULT and resets the controller.\n\nNo data is copied, so this is not memory corruption.  What a controller\ngets is a kernel warning it can raise at will, which is fatal on a host\nbooted with panic_on_warn.\n\nThe send path already knows the direction - it consults rq_data_dir()\nwhen it builds a command - and nvme_tcp_handle_r2t() checks the length\nand the offset of the request it names.  The C2HData path does not check\nthe direction at all.\n\nReject a C2HData PDU whose command is not a read.  Rejecting it fails\nthe command and resets the controller, as the neighbouring check in this\nfunction does; what goes away is the warning.\n\n  [    6.885580] ------------[ cut here ]------------\n  [    6.886457] WARNING: lib/iov_iter.c:193 at _copy_to_iter+0x289/0x1330, CPU#0: kworker/0:1H/71\n  [    6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy)\n  [    6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work\n  [    6.891875] RIP: 0010:_copy_to_iter+0x289/0x1330\n  [    6.903739] Call Trace:\n  [    6.904085]  \u0026lt;TASK\u0026gt;\n  [    6.909254]  __skb_datagram_iter+0x433/0x820\n  [    6.911026]  skb_copy_datagram_iter+0x37/0x120\n  [    6.911622]  nvme_tcp_recv_skb+0xa07/0x4320\n  [    6.913378]  __tcp_read_sock+0x1ab/0x810\n  [    6.915788]  nvme_tcp_try_recv+0x152/0x1e0\n  [    6.918222]  nvme_tcp_io_work+0x1e4/0x6c0\n  [    6.926906]  \u0026lt;/TASK\u0026gt;\n  [    6.927226] ---[ end trace 0000000000000000 ]---\n  [    6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data\n  [    6.928709] nvme nvme0: receive failed:  -14(CVE-2026-89973)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndma-direct: return struct page from dma_direct_alloc_from_pool()\n\nCommit 5b138c534fda (\u0026quot;dma-direct: factor out a dma_direct_alloc_from_pool\nhelper\u0026quot;) changed dma_direct_alloc_from_pool() to return the CPU address\nfrom dma_alloc_from_pool(). That fits dma_direct_alloc(), but\ndma_direct_alloc_pages() also uses the helper and expects a struct page *.\n\nFix this by making dma_direct_alloc_from_pool() return the struct page *\nagain, and pass the CPU address back through an out-parameter for the\ndma_direct_alloc() caller.(CVE-2026-89995)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix OOB altmode array index\n\nThe UCSI displayport driver indexes the connector\u0026apos;s port altmode array\nwith the GET_CURRENT_CAM response after checking it is not 0xff. The\nport altmode array is UCSI_MAX_ALTMODES elements long. If the PPM\nreturns an invalid GET_CURRENT_CAM response above UCSI_MAX_ALTMODES and\nnot equal to 0xff, the kernel may crash with an array index OOB error.\n\nUpdate the UCSI displayport driver to verify the current cam is less\nthan UCSI_MAX_ALTMODES before accessing the port altmode array.(CVE-2026-90025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pnfs: key the data server cache on the NFS version\n\nnfs4_pnfs_ds_add() keys the per-net data server cache on the multipath\naddress set alone, and struct nfs4_pnfs_ds records no version. That\nsuffices for the files layout driver, which always connects with version\n4, but flexfiles takes its version tuple from GETDEVICEINFO per device,\nand one address can legitimately serve both NFSv3 and NFSv4.\n\nTwo deviceids on one address with different ds_versions[0].version\ntherefore share a single nfs4_pnfs_ds, and whichever mirror connects\nfirst pins ds_clp to its own version. The other one is handed that\nclient anyway, so it selects rpc_call_ops for a version the connection\ndoes not speak, and the mismatched sequence-slot handling dereferences\nNULL.\n\nAdd the version to the cache key so the two cannot alias, giving each\nversion its own nfs4_pnfs_ds and connection while both mirrors stay\nusable. Only the major version is compared, since that is what selects\nrpc_call_ops and rpc_ops; v4.0 and v4.1 keep sharing a client. The files\nlayout driver passes the 4 it already hardcodes at connect time.(CVE-2026-90102)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Return a delegation the client fails to record\n\nWhen an NFS server grants a delegation in an OPEN reply,\nnfs_inode_set_delegation() records it on the client. However, three\nof its error flows return without sending DELEGRETURN.\n\nA delegation can be relinquished only by DELEGRETURN (RFC 8881\nSection 20.2.4), so dropping one silently leaves the server believing\nthe client still holds it. If the server happens to recall that\ndelegation, the client answers CB_RECALL with NFS4ERR_BADHANDLE\nbecause it has no record of the stateid. The server revokes the\ndelegation and moves it onto its cl_revoked list, because the client\nnever sends the FREE_STATEID that would drain it. Every subsequent\nSEQUENCE reply then carries SEQ4_STATUS_RECALLABLE_STATE_REVOKED,\nand the client\u0026apos;s state manager loops issuing TEST_STATEID across its\ndelegations without ever clearing the condition.\n\nThe window is easy to reach now that a server offers a write\ndelegation on any write OPEN: a delegation recalled for one opener\nraces a re-open that the server answers with a fresh write\ndelegation.\n\nInstead of dropping it, hand the delegation back during these error\nflows.(CVE-2026-90234)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/omap: dsi: Do not copy isr table\n\nTo be able to unregister stuff from isrs, the corresponding table was\ncopied.  Nobody seems to unregister stuff that way, so it does not help.\nBut there are stack-allocated objects passed to these isrs giving chances\nof UAF of these objects if irqs are unregistered while they are handled,\nso better do not copy that table.(CVE-2026-90316)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: synchronize input before cleaning up a failed probe\n\nhid_device_io_start() allows reports to run concurrently with probe. If\nthe probe subsequently fails, __hid_device_probe() releases driver\nresources and clears hdev-\u0026gt;driver without first excluding those report\ncallbacks.\n\nFor example, a report may enter hidraw_report_event() while the failure\npath frees the associated hidraw object, leading to a use-after-free when\nthe report takes the object\u0026apos;s list lock.\n\nStop input before performing failed-probe cleanup. This reacquires\ndriver_input_lock and waits for any report callback already in progress.(CVE-2026-90329)","status":"published","published":"2026-10-16T11:59:44Z","modified":"2026-10-16T12:15:15.099429143Z","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.981622Z"},{"id":"UBUNTU-CVE-2026-80551","description":"In the Linux kernel, the following vulnerability has been resolved: s390/vfio_ccw: Ensure first IDAW remains constant The first IDAW in a list does not need to be on a 2K/4K boundary like all others, and so is read separately to accurately calculate the size of the buffer needed to read the full IDAL. Verify that the address found in the first IDAW is unchanged between reads, to ensure a consistent set of IDAWs being worked with.","status":"published","published":"2026-08-26T15:17:00Z","modified":"2026-11-10T02:51:44.048150701Z","cvss":[{"version":"4.0","score":8.9,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","level":"high"},{"version":"3.1","score":9.3,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-10T03:20:27.246625Z"},{"id":"AZL-97824","title":"CVE-2026-80551 affecting package kernel for versions less than 6.6.157.1-1","description":"In 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.","status":"published","published":"2026-08-26T15:17:09Z","modified":"2026-10-02T14:19:12.120440371Z","updated_at":"2026-11-02T15:28:12.313414Z"},{"id":"MGASA-2026-0506","title":"Updated kernel, drakx-installer-images, kmod-nvidia-current-wopengpu, kmod-xtables-addons \u0026 kmod-virtualbox packages fix Security Vulnerabilities","description":"Upstream kernel 6.18.55 version fixes bugs and vulnerabilities.\nThe kmod-xtables-addons, kmod-virtualbox, kmod-nvidia-current-wopengpu \u0026\ndrakx-installer-images packages have been updated to work with this new\nkernel.\n","status":"published","published":"2026-10-15T05:34:04Z","modified":"2026-10-15T05:45:03.401041509Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"MGASA-2026-0542","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.18.55 fixes vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-10-25T02:36:50Z","modified":"2026-10-25T02:45:03.29833395Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"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"}]}}