{"id":"CVE-2026-23047","aliases":["BELL-CVE-2026-23047","DEBIAN-CVE-2026-23047","DLA-4475-1","DLA-4476-1","DSA-6126-1","DSA-6127-1","EUVD-2026-5500","GHSA-484m-2c5w-2g38","MGASA-2026-0097","MGASA-2026-0098","OESA-2026-1566","OESA-2026-1567","OESA-2026-1570","ROOT-OS-DEBIAN-11-CVE-2026-23047","ROOT-OS-DEBIAN-12-CVE-2026-23047","ROOT-OS-UBUNTU-2404-CVE-2026-23047","SUSE-SU-2026:1573-1","SUSE-SU-2026:1661-1","SUSE-SU-2026:20838-1","SUSE-SU-2026:20873-1","SUSE-SU-2026:20931-1","SUSE-SU-2026:21114-1","SUSE-SU-2026:21123-1","SUSE-SU-2026:21255-1","SUSE-SU-2026:21284-1","UBUNTU-CVE-2026-23047","USN-8096-1","USN-8096-2","USN-8096-3","USN-8096-4","USN-8096-5","USN-8116-1","USN-8141-1","USN-8163-1","USN-8163-2","USN-8243-1","USN-8278-1","USN-8278-2","USN-8289-1","USN-8289-2","USN-8296-1","USN-8296-2","USN-8393-1","USN-8440-1","USN-8499-1","USN-8570-1","USN-8570-2","USN-8594-1","USN-8604-1","USN-8605-1","USN-8669-1","openSUSE-SU-2026:20416-1"],"status":"published","title":"libceph: make calc_target() set t-\u003epaused, not just clear it","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","from":"osv"},"epss":{"day":"2026-11-12","score":0.00193,"percentile":0.0911,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-02-04T16:00:29Z","modified":"2026-11-11T09:39:27Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.161-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.66-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.10.248","5.15.198","6.1.161","6.6.121","6.12.66","6.18.6"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.162-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.69-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.18.8-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1103.110~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1110.119~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1103.112~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-173.183~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1097.100~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1098.104~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-173.183~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1055.55~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1100.106~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1097.101~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-173.183"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1103.110"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1057.60~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1109.118"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1059.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1109.118.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1058.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1103.112"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1060.63~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1099.105"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1086.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-124.124~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1097.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1055.56~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1098.104"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1095.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-173.183"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-117.117.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1098.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1054.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1055.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1044.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1100.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1054.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1097.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-117.117~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1067.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1086.88"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1094.96"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1102.111"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1051.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1103.110+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1109.118+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-173.183+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1103.112+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-117.117"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1055.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1056.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","fixed_in":["6.17.0-1021.21~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1058.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1039.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1021.24~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1054.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1041.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","fixed_in":["6.17.0-41.41~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1055.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-117.117.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1031.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1054.57.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1030.30"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1054.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1019.19~24.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1056.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1032.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1022.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1051.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1018.20~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1055.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1059.65+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-116.116+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1058.61+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.159-r0"},{"fixed":"6.1.161-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.65-r0"},{"fixed":"6.12.66-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.7.0"},{"fixed":"5.10.248"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.198"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.161"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.121"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.66"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.6"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.8-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.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.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-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"]},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.249-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.223-1","5.10.226-1","5.10.234-1","5.10.237-1","5.10.244-1","5.10.247-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":165},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1","6.1.119-1~deb11u1","6.1.128-1~deb11u1","6.1.129-1~deb11u1","6.1.137-1~deb11u1","6.1.140-1~deb11u1","6.1.147-1~deb11u1","6.1.148-1~deb11u1","6.1.153-1~deb11u1","6.1.158-1~deb11u1","6.1.159-1~deb11u1"],"bundled":252},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"],"bundled":251},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"bundled":252},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-15.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-89.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.136.oe2403sp1"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.137.oe2403sp2"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.124.oe2403"}]}],"bundled":73},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.1"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.37.2"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.37.2"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.37.1"}]}],"bundled":40},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1.21.18"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":61},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-41.1"}]}],"bundled":59},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1023.24~14.04.1","4.15.0-1030.31~14.04.1","4.15.0-1031.32~14.04.1","4.15.0-1032.33~14.04.2","4.15.0-1035.36~14.04.2","4.15.0-1036.38~14.04.2","4.15.0-1037.39~14.04.2","4.15.0-1039.41~14.04.2","4.15.0-1040.44~14.04.1","4.15.0-1041.45~14.04.1","4.15.0-1042.46~14.04.1","4.15.0-1045.49~14.04.1","4.15.0-1046.50~14.04.1","4.15.0-1047.51~14.04.1","4.15.0-1049.54~14.04.1","4.15.0-1050.55~14.04.1","4.15.0-1051.56~14.04.1","4.15.0-1052.57~14.04.1","4.15.0-1055.60~14.04.1","4.15.0-1056.61~14.04.1","4.15.0-1057.62~14.04.1","4.15.0-1059.64~14.04.1","4.15.0-1060.65~14.04.1","4.15.0-1061.66~14.04.1","4.15.0-1063.68~14.04.1","4.15.0-1064.69~14.04.1","4.15.0-1066.71~14.04.1","4.15.0-1067.72~14.04.1","4.15.0-1069.74~14.04.1","4.15.0-1071.76~14.04.1","4.15.0-1074.79~14.04.1","4.15.0-1077.82~14.04.1","4.15.0-1082.92~14.04.1","4.15.0-1083.93~14.04.1","4.15.0-1089.99~14.04.1","4.15.0-1091.101~14.04.1","4.15.0-1092.102~14.04.1","4.15.0-1093.103~14.04.1","4.15.0-1095.105~14.04.1","4.15.0-1096.106~14.04.1","4.15.0-1098.109~14.04.1","4.15.0-1100.111~14.04.1","4.15.0-1102.113~14.04.1","4.15.0-1103.114~14.04.1","4.15.0-1106.118~14.04.1","4.15.0-1108.120~14.04.1","4.15.0-1109.121~14.04.1","4.15.0-1110.122~14.04.1","4.15.0-1111.123~14.04.1","4.15.0-1112.124~14.04.1","4.15.0-1113.126~14.04.1","4.15.0-1114.127~14.04.1","4.15.0-1115.128~14.04.1","4.15.0-1118.131~14.04.1","4.15.0-1121.134~14.04.1","4.15.0-1122.135~14.04.1","4.15.0-1123.136~14.04.1","4.15.0-1124.137~14.04.1","4.15.0-1125.138~14.04.1","4.15.0-1126.139~14.04.1","4.15.0-1127.140~14.04.1","4.15.0-1129.142~14.04.1","4.15.0-1130.143~14.04.1","4.15.0-1131.144~14.04.1","4.15.0-1133.146~14.04.1","4.15.0-1134.147~14.04.1","4.15.0-1136.149~14.04.1","4.15.0-1137.150~14.04.1","4.15.0-1138.151~14.04.1","4.15.0-1139.152~14.04.1","4.15.0-1142.156~14.04.1","4.15.0-1145.160~14.04.1","4.15.0-1146.161~14.04.1","4.15.0-1149.164~14.04.1","4.15.0-1150.165~14.04.1","4.15.0-1151.166~14.04.1","4.15.0-1153.168~14.04.1","4.15.0-1157.172~14.04.2","4.15.0-1158.173~14.04.1","4.15.0-1159.174~14.04.1","4.15.0-1162.177~14.04.1","4.15.0-1163.178~14.04.1","4.15.0-1164.179~14.04.1","4.15.0-1165.180~14.04.1","4.15.0-1166.181~14.04.1","4.15.0-1167.182~14.04.1","4.15.0-1168.183~14.04.1","4.15.0-1169.184~14.04.1","4.15.0-1170.185~14.04.1","4.15.0-1171.186~14.04.1","4.15.0-1172.187~14.04.1","4.15.0-1173.188~14.04.1","4.15.0-1174.189~14.04.1","4.15.0-1175.190~14.04.1","4.15.0-1176.191~14.04.1","4.15.0-1177.192~14.04.1","4.15.0-1178.193~14.04.1","4.15.0-1179.194~14.04.1","4.15.0-1180.195~14.04.1","4.15.0-1181.196~14.04.1","4.15.0-1182.197~14.04.1","4.15.0-1183.198~14.04.1","4.15.0-1184.199~14.04.1","4.15.0-1185.200~14.04.1","4.15.0-1186.201~14.04.1","4.15.0-1187.202~14.04.1","4.15.0-1188.203~14.04.1","4.15.0-1189.204~14.04.1","4.15.0-1190.205~14.04.1","4.15.0-1191.206~14.04.1","4.15.0-1192.207~14.04.1","4.15.0-1193.208~14.04.1","4.15.0-1194.209~14.04.1","4.15.0-1195.210~14.04.1","4.15.0-1196.211~14.04.1","4.15.0-1197.212~14.04.1","4.15.0-1199.214~14.04.1","4.15.0-1200.215~14.04.1","4.15.0-1201.216~14.04.1","4.15.0-1202.217~14.04.1","4.15.0-1205.220~14.04.1","4.15.0-1206.221~14.04.1","4.15.0-1207.222~14.04.1","4.15.0-1208.223~14.04.1","4.15.0-1209.224~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1","4.15.0-1176.189~16.04.1","4.15.0-1177.190~16.04.1","4.15.0-1178.191~16.04.1","4.15.0-1179.192~16.04.1","4.15.0-1180.193~16.04.1","4.15.0-1181.194~16.04.1","4.15.0-1182.195~16.04.1","4.15.0-1183.196~16.04.1","4.15.0-1184.197~16.04.1","4.15.0-1185.198~16.04.1","4.15.0-1186.199~16.04.1","4.15.0-1187.200~16.04.1","4.15.0-1188.201~16.04.1","4.15.0-1189.202~16.04.1","4.15.0-1190.203~16.04.1","4.15.0-1191.204~16.04.1","4.15.0-1192.205~16.04.1","4.15.0-1194.207~16.04.1","4.15.0-1195.208~16.04.1","4.15.0-1196.209~16.04.1","4.15.0-1197.210~16.04.1","4.15.0-1198.211~16.04.1","4.15.0-1199.212~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1","4.15.0-1184.199~16.04.1","4.15.0-1185.200~16.04.1","4.15.0-1186.201~16.04.1","4.15.0-1187.202~16.04.1","4.15.0-1188.203~16.04.1","4.15.0-1189.204~16.04.1","4.15.0-1190.205~16.04.1","4.15.0-1191.206~16.04.1","4.15.0-1192.207~16.04.1","4.15.0-1193.208~16.04.1","4.15.0-1194.209~16.04.1","4.15.0-1195.210~16.04.1","4.15.0-1196.211~16.04.1","4.15.0-1197.212~16.04.1","4.15.0-1200.215~16.04.1","4.15.0-1204.219~16.04.1","4.15.0-1205.220~16.04.1","4.15.0-1206.221~16.04.1","4.15.0-1208.223~16.04.1","4.15.0-1209.224~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1","4.15.0-1169.186~16.04.1","4.15.0-1170.187~16.04.1","4.15.0-1171.188~16.04.1","4.15.0-1172.189~16.04.1","4.15.0-1173.190~16.04.1","4.15.0-1174.191~16.04.1","4.15.0-1175.192~16.04.1","4.15.0-1176.193~16.04.1","4.15.0-1177.194~16.04.1","4.15.0-1178.195~16.04.1","4.15.0-1179.196~16.04.1","4.15.0-1180.197~16.04.1","4.15.0-1181.198~16.04.1","4.15.0-1182.199~16.04.1","4.15.0-1183.200~16.04.2","4.15.0-1184.201~16.04.1","4.15.0-1185.202~16.04.1","4.15.0-1187.204~16.04.1","4.15.0-1188.205~16.04.1","4.15.0-1189.206~16.04.1","4.15.0-1190.207~16.04.1","4.15.0-1191.208~16.04.1","4.15.0-1192.209~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1","4.15.0-232.244~16.04.1","4.15.0-233.245~16.04.1","4.15.0-234.246~16.04.1","4.15.0-235.247~16.04.1","4.15.0-236.248~16.04.1","4.15.0-237.249~16.04.1","4.15.0-238.250~16.04.1","4.15.0-239.251~16.04.1","4.15.0-240.252~16.04.1","4.15.0-241.253~16.04.1","4.15.0-242.254~16.04.1","4.15.0-243.255~16.04.1","4.15.0-245.257~16.04.1","4.15.0-246.258~16.04.1","4.15.0-247.259~16.04.1","4.15.0-248.260~16.04.1","4.15.0-249.261~16.04.1","4.15.0-250.262~16.04.1","4.15.0-253.265~16.04.1","4.15.0-254.266~16.04.1","4.15.0-257.269~16.04.1","4.15.0-260.272~16.04.2","4.15.0-261.273~16.04.1","4.15.0-262.274~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1138.149~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.153~16.04.1","4.15.0-1143.154~16.04.1","4.15.0-1144.155~16.04.1","4.15.0-1145.156~16.04.1","4.15.0-1148.159~16.04.1","4.15.0-1149.160~16.04.1","4.15.0-1150.161~16.04.1","4.15.0-1151.162~16.04.1","4.15.0-1153.164~16.04.1","4.15.0-1154.165~16.04.1","4.15.0-1156.167~16.04.1","4.15.0-1158.169~16.04.1","4.15.0-1160.171~16.04.1","4.15.0-1161.172~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243","4.15.0-232.244","4.15.0-233.245","4.15.0-234.246","4.15.0-235.247","4.15.0-236.248","4.15.0-237.249","4.15.0-238.250","4.15.0-239.251","4.15.0-240.252","4.15.0-241.253","4.15.0-242.254","4.15.0-243.255","4.15.0-245.257","4.15.0-246.258","4.15.0-247.259","4.15.0-248.260","4.15.0-249.261","4.15.0-250.262","4.15.0-251.263","4.15.0-253.265","4.15.0-254.266","4.15.0-257.269","4.15.0-260.272","4.15.0-261.273","4.15.0-262.274"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188","4.15.0-1176.189","4.15.0-1177.190","4.15.0-1178.191","4.15.0-1179.192","4.15.0-1180.193","4.15.0-1181.194","4.15.0-1182.195","4.15.0-1183.196","4.15.0-1184.197","4.15.0-1185.198","4.15.0-1186.199","4.15.0-1187.200","4.15.0-1188.201","4.15.0-1189.202","4.15.0-1190.203","4.15.0-1191.204","4.15.0-1192.205","4.15.0-1194.207","4.15.0-1195.208","4.15.0-1196.209","4.15.0-1197.210","4.15.0-1198.211","4.15.0-1199.212"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1018.18~18.04.1","5.4.0-1020.20~18.04.2","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.30~18.04.1","5.4.0-1030.31~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1038.40~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1045.47~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1058.61~18.04.3","5.4.0-1059.62~18.04.1","5.4.0-1060.63~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1081.88~18.04.1","5.4.0-1083.90~18.04.1","5.4.0-1084.91~18.04.1","5.4.0-1085.92~18.04.1","5.4.0-1086.93~18.04.1","5.4.0-1088.96~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1090.98~18.04.1","5.4.0-1092.100~18.04.2","5.4.0-1093.102~18.04.2","5.4.0-1094.102~18.04.1","5.4.0-1096.104~18.04.1","5.4.0-1097.105~18.04.1","5.4.0-1099.107~18.04.1","5.4.0-1100.108~18.04.1","5.4.0-1101.109~18.04.1","5.4.0-1103.111~18.04.1","5.4.0-1104.112~18.04.1","5.4.0-1105.113~18.04.1","5.4.0-1106.114~18.04.1","5.4.0-1107.115~18.04.1","5.4.0-1108.116~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.2","5.4.0-1113.123~18.04.1","5.4.0-1114.124~18.04.1","5.4.0-1116.126~18.04.1","5.4.0-1117.127~18.04.1","5.4.0-1118.128~18.04.1","5.4.0-1119.129~18.04.1","5.4.0-1120.130~18.04.1","5.4.0-1121.131~18.04.1","5.4.0-1122.132~18.04.1","5.4.0-1123.133~18.04.1","5.4.0-1124.134~18.04.1","5.4.0-1125.135~18.04.1","5.4.0-1126.136~18.04.1","5.4.0-1127.137~18.04.2","5.4.0-1128.138~18.04.1","5.4.0-1129.139~18.04.1","5.4.0-1130.140~18.04.1","5.4.0-1131.141~18.04.1","5.4.0-1132.142~18.04.1","5.4.0-1133.143~18.04.1","5.4.0-1134.144~18.04.1","5.4.0-1135.145~18.04.1","5.4.0-1136.146~18.04.1","5.4.0-1137.147~18.04.1","5.4.0-1139.149~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1147.157~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1153.163~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1156.166~18.04.1","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1160.170~18.04.1","5.4.0-1161.172~18.04.1","5.4.0-1162.173~18.04.1","5.4.0-1163.174~18.04.1","5.4.0-1165.176~18.04.1","5.4.0-1167.178~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1082.92","4.15.0-1083.93","4.15.0-1089.99","4.15.0-1091.101","4.15.0-1092.102","4.15.0-1093.103","4.15.0-1095.105","4.15.0-1096.106","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1102.113","4.15.0-1103.114","4.15.0-1104.116","4.15.0-1106.118","4.15.0-1108.120","4.15.0-1109.121","4.15.0-1110.122","4.15.0-1111.123","4.15.0-1112.125","4.15.0-1113.126","4.15.0-1114.127","4.15.0-1115.128","4.15.0-1118.131","4.15.0-1121.134","4.15.0-1122.135","4.15.0-1123.136","4.15.0-1124.137","4.15.0-1125.138","4.15.0-1126.139","4.15.0-1127.140","4.15.0-1129.142","4.15.0-1130.143","4.15.0-1131.144","4.15.0-1133.146","4.15.0-1134.147","4.15.0-1136.149","4.15.0-1137.150","4.15.0-1138.151","4.15.0-1139.152","4.15.0-1142.156","4.15.0-1145.160","4.15.0-1146.161","4.15.0-1149.164","4.15.0-1150.165","4.15.0-1151.166","4.15.0-1153.168","4.15.0-1157.172","4.15.0-1158.173","4.15.0-1159.174","4.15.0-1161.176","4.15.0-1162.177","4.15.0-1163.178","4.15.0-1164.179","4.15.0-1165.180","4.15.0-1166.181","4.15.0-1167.182","4.15.0-1168.183","4.15.0-1169.184","4.15.0-1170.185","4.15.0-1171.186","4.15.0-1172.187","4.15.0-1173.188","4.15.0-1174.189","4.15.0-1175.190","4.15.0-1176.191","4.15.0-1177.192","4.15.0-1178.193","4.15.0-1179.194","4.15.0-1180.195","4.15.0-1181.196","4.15.0-1182.197","4.15.0-1183.198","4.15.0-1184.199","4.15.0-1185.200","4.15.0-1186.201","4.15.0-1187.202","4.15.0-1188.203","4.15.0-1189.204","4.15.0-1190.205","4.15.0-1191.206","4.15.0-1192.207","4.15.0-1193.208","4.15.0-1194.209","4.15.0-1195.210","4.15.0-1196.211","4.15.0-1197.212","4.15.0-1199.214","4.15.0-1200.215","4.15.0-1201.216","4.15.0-1202.217","4.15.0-1204.219","4.15.0-1205.220","4.15.0-1206.221","4.15.0-1207.222","4.15.0-1208.223","4.15.0-1209.224"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-azure-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.20~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1023.23~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1026.26~18.04.1","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1035.36~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1041.43~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1047.49~18.04.1","5.4.0-1048.50~18.04.1","5.4.0-1049.51~18.04.1","5.4.0-1051.53~18.04.1","5.4.0-1055.57~18.04.1","5.4.0-1056.58~18.04.1","5.4.0-1058.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1064.67~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1069.72~18.04.1","5.4.0-1070.73~18.04.1","5.4.0-1072.75~18.04.1","5.4.0-1073.76~18.04.1","5.4.0-1074.77~18.04.1","5.4.0-1077.80~18.04.1","5.4.0-1078.81~18.04.1","5.4.0-1080.83~18.04.2","5.4.0-1083.87~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1089.94~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1091.96~18.04.1","5.4.0-1094.100~18.04.1","5.4.0-1095.101~18.04.1","5.4.0-1098.104~18.04.2","5.4.0-1100.106~18.04.1","5.4.0-1101.107~18.04.1","5.4.0-1103.109~18.04.1","5.4.0-1104.110~18.04.1","5.4.0-1105.111~18.04.1","5.4.0-1106.112~18.04.1","5.4.0-1107.113~18.04.1","5.4.0-1108.114~18.04.1","5.4.0-1109.115~18.04.1","5.4.0-1110.116~18.04.1","5.4.0-1111.117~18.04.1","5.4.0-1112.118~18.04.1","5.4.0-1113.119~18.04.1","5.4.0-1115.122~18.04.1","5.4.0-1116.123~18.04.1","5.4.0-1117.124~18.04.1","5.4.0-1118.125~18.04.1","5.4.0-1119.126~18.04.2","5.4.0-1120.127~18.04.1","5.4.0-1121.128~18.04.1","5.4.0-1122.129~18.04.1","5.4.0-1123.130~18.04.1","5.4.0-1124.131~18.04.1","5.4.0-1126.133~18.04.1","5.4.0-1127.134~18.04.1","5.4.0-1128.135~18.04.1","5.4.0-1129.136~18.04.1","5.4.0-1130.137~18.04.1","5.4.0-1131.138~18.04.1","5.4.0-1132.139~18.04.1","5.4.0-1133.140~18.04.1","5.4.0-1134.141~18.04.1","5.4.0-1135.142~18.04.1","5.4.0-1136.143~18.04.1","5.4.0-1137.144~18.04.1","5.4.0-1138.145~18.04.1","5.4.0-1139.146~18.04.1","5.4.0-1140.147~18.04.1","5.4.0-1142.149~18.04.1","5.4.0-1143.150~18.04.1","5.4.0-1145.152~18.04.1","5.4.0-1147.154~18.04.1","5.4.0-1148.155~18.04.1","5.4.0-1149.156~18.04.1","5.4.0-1150.157~18.04.1","5.4.0-1151.158~18.04.1","5.4.0-1152.159~18.04.1","5.4.0-1153.160~18.04.1","5.4.0-1154.161~18.04.1","5.4.0-1156.163~18.04.1","5.4.0-1157.164~18.04.1","5.4.0-1161.167~18.04.1","5.4.0-1162.168~18.04.1","5.4.0-1163.169~18.04.1","5.4.0-1164.170~18.04.1","5.4.0-1166.172~18.04.1","5.4.0-1167.173~18.04.1","5.4.0-1168.174~18.04.1","5.4.0-1169.175~18.04.1","5.4.0-1170.176~18.04.1","5.4.0-1171.177~18.04.1","5.4.0-1172.178~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1071.81","4.15.0-1077.87","4.15.0-1078.88","4.15.0-1080.90","4.15.0-1081.92","4.15.0-1083.94","4.15.0-1084.95","4.15.0-1086.98","4.15.0-1087.100","4.15.0-1088.101","4.15.0-1090.103","4.15.0-1091.104","4.15.0-1092.105","4.15.0-1093.106","4.15.0-1094.107","4.15.0-1095.108","4.15.0-1096.109","4.15.0-1097.110","4.15.0-1098.111","4.15.0-1099.112","4.15.0-1100.113","4.15.0-1103.116","4.15.0-1106.120","4.15.0-1107.121","4.15.0-1108.122","4.15.0-1109.123","4.15.0-1110.124","4.15.0-1111.125","4.15.0-1112.126","4.15.0-1114.128","4.15.0-1115.129","4.15.0-1116.130","4.15.0-1118.132","4.15.0-1119.133","4.15.0-1120.134","4.15.0-1121.135","4.15.0-1122.136","4.15.0-1124.138","4.15.0-1127.142","4.15.0-1130.146","4.15.0-1131.147","4.15.0-1134.150","4.15.0-1135.151","4.15.0-1136.152","4.15.0-1137.153","4.15.0-1138.154","4.15.0-1141.157","4.15.0-1142.158","4.15.0-1143.159","4.15.0-1145.161","4.15.0-1146.162","4.15.0-1147.163","4.15.0-1148.164","4.15.0-1149.165","4.15.0-1150.166","4.15.0-1151.167","4.15.0-1152.168","4.15.0-1153.170","4.15.0-1154.171","4.15.0-1155.172","4.15.0-1156.173","4.15.0-1157.174","4.15.0-1158.175","4.15.0-1159.176","4.15.0-1160.177","4.15.0-1161.178","4.15.0-1162.179","4.15.0-1163.180","4.15.0-1164.181","4.15.0-1165.182","4.15.0-1166.183","4.15.0-1167.184","4.15.0-1168.185","4.15.0-1169.186","4.15.0-1170.187","4.15.0-1171.188","4.15.0-1172.189","4.15.0-1173.190","4.15.0-1174.191","4.15.0-1175.192","4.15.0-1176.193","4.15.0-1177.194","4.15.0-1178.195","4.15.0-1179.196","4.15.0-1180.197","4.15.0-1181.198","4.15.0-1182.199","4.15.0-1183.200","4.15.0-1184.201","4.15.0-1185.202","4.15.0-1186.203","4.15.0-1187.204","4.15.0-1188.205","4.15.0-1189.206","4.15.0-1190.207","4.15.0-1191.208","4.15.0-1192.209"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-gcp-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.2","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1040.43~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.2","5.4.0-1046.49~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1051.55~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1060.64~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1065.69~18.04.1","5.4.0-1067.71~18.04.1","5.4.0-1068.72~18.04.1","5.4.0-1069.73~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.87~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.94~18.04.1","5.4.0-1087.95~18.04.1","5.4.0-1089.97~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1096.105~18.04.2","5.4.0-1097.106~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.2","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.1","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1128.137~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1139.148~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.150~18.04.1","5.4.0-1142.151~18.04.1","5.4.0-1143.152~18.04.1","5.4.0-1145.154~18.04.1","5.4.0-1147.156~18.04.1","5.4.0-1148.157~18.04.1","5.4.0-1149.158~18.04.1","5.4.0-1150.159~18.04.1","5.4.0-1151.160~18.04.1","5.4.0-1152.161~18.04.1","5.4.0-1153.162~18.04.1","5.4.0-1154.163~18.04.1","5.4.0-1155.164~18.04.1","5.4.0-1156.165~18.04.1","5.4.0-1157.166~18.04.1","5.4.0-1159.168~18.04.1","5.4.0-1160.169~18.04.1","5.4.0-1161.170~18.04.1","5.4.0-1162.171~18.04.1","5.4.0-1163.172~18.04.1","5.4.0-1164.173~18.04.1","5.4.0-1165.174~18.04.1","5.4.0-1166.175~18.04.1","5.4.0-1167.176~18.04.1","5.4.0-1168.178~18.04.1","5.4.0-1169.179~18.04.1","5.4.0-1170.180~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-hwe-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-37.41~18.04.1","5.4.0-39.43~18.04.1","5.4.0-40.44~18.04.1","5.4.0-42.46~18.04.1","5.4.0-45.49~18.04.2","5.4.0-47.51~18.04.1","5.4.0-48.52~18.04.1","5.4.0-51.56~18.04.1","5.4.0-52.57~18.04.1","5.4.0-53.59~18.04.1","5.4.0-54.60~18.04.1","5.4.0-56.62~18.04.1","5.4.0-58.64~18.04.1","5.4.0-59.65~18.04.1","5.4.0-60.67~18.04.1","5.4.0-62.70~18.04.1","5.4.0-64.72~18.04.1","5.4.0-65.73~18.04.1","5.4.0-66.74~18.04.2","5.4.0-67.75~18.04.1","5.4.0-70.78~18.04.1","5.4.0-71.79~18.04.1","5.4.0-72.80~18.04.1","5.4.0-73.82~18.04.1","5.4.0-74.83~18.04.1","5.4.0-77.86~18.04.1","5.4.0-80.90~18.04.1","5.4.0-81.91~18.04.1","5.4.0-84.94~18.04.1","5.4.0-86.97~18.04.1","5.4.0-87.98~18.04.1","5.4.0-89.100~18.04.1","5.4.0-90.101~18.04.1","5.4.0-91.102~18.04.1","5.4.0-92.103~18.04.2","5.4.0-94.106~18.04.1","5.4.0-96.109~18.04.1","5.4.0-97.110~18.04.1","5.4.0-99.112~18.04.1","5.4.0-100.113~18.04.1","5.4.0-104.118~18.04.1","5.4.0-105.119~18.04.1","5.4.0-107.121~18.04.1","5.4.0-109.123~18.04.1","5.4.0-110.124~18.04.1","5.4.0-113.127~18.04.1","5.4.0-117.132~18.04.1","5.4.0-120.136~18.04.1","5.4.0-121.137~18.04.1","5.4.0-122.138~18.04.1","5.4.0-124.140~18.04.1","5.4.0-125.141~18.04.1","5.4.0-126.142~18.04.1","5.4.0-128.144~18.04.1","5.4.0-131.147~18.04.1","5.4.0-132.148~18.04.1","5.4.0-133.149~18.04.1","5.4.0-135.152~18.04.2","5.4.0-136.153~18.04.1","5.4.0-137.154~18.04.1","5.4.0-139.156~18.04.1","5.4.0-144.161~18.04.1","5.4.0-146.163~18.04.1","5.4.0-147.164~18.04.1","5.4.0-148.165~18.04.1","5.4.0-149.166~18.04.1","5.4.0-150.167~18.04.1","5.4.0-152.169~18.04.1","5.4.0-153.170~18.04.1","5.4.0-155.172~18.04.1","5.4.0-156.173~18.04.1","5.4.0-159.176~18.04.1","5.4.0-162.179~18.04.1","5.4.0-163.180~18.04.1","5.4.0-164.181~18.04.1","5.4.0-165.182~18.04.1","5.4.0-166.183~18.04.2","5.4.0-167.184~18.04.1","5.4.0-169.187~18.04.1","5.4.0-170.188~18.04.1","5.4.0-171.189~18.04.1","5.4.0-172.190~18.04.1","5.4.0-173.191~18.04.1","5.4.0-174.193~18.04.1","5.4.0-175.195~18.04.1","5.4.0-177.197~18.04.1","5.4.0-181.201~18.04.1","5.4.0-182.202~18.04.1","5.4.0-186.206~18.04.1","5.4.0-187.207~18.04.1","5.4.0-189.209~18.04.1","5.4.0-190.210~18.04.1","5.4.0-192.212~18.04.1","5.4.0-193.213~18.04.1","5.4.0-195.215~18.04.1","5.4.0-196.216~18.04.1","5.4.0-198.218~18.04.1","5.4.0-200.220~18.04.1","5.4.0-202.222~18.04.1","5.4.0-204.224~18.04.1","5.4.0-205.225~18.04.1","5.4.0-208.228~18.04.1","5.4.0-211.231~18.04.1","5.4.0-212.232~18.04.1","5.4.0-214.234~18.04.1","5.4.0-215.235~18.04.1","5.4.0-216.236~18.04.1","5.4.0-218.238~18.04.1","5.4.0-219.239~18.04.1","5.4.0-220.240~18.04.1","5.4.0-221.241~18.04.1","5.4.0-222.242~18.04.1","5.4.0-223.243~18.04.1","5.4.0-224.244~18.04.1","5.4.0-225.245~18.04.1","5.4.0-227.247~18.04.1","5.4.0-228.248~18.04.1","5.4.0-229.249~18.04.1","5.4.0-231.251~18.04.1","5.4.0-233.253~18.04.1","5.4.0-234.254~18.04.1","5.4.0-238.258~18.04.1","5.4.0-241.261~18.04.1","5.4.0-242.262~18.04.1","5.4.0-244.264~18.04.1","5.4.0-245.265~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-ibm-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1010.11~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1017.19~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1020.22~18.04.1","5.4.0-1021.23~18.04.1","5.4.0-1023.25~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.32~18.04.1","5.4.0-1029.33~18.04.1","5.4.0-1031.35~18.04.1","5.4.0-1032.36~18.04.1","5.4.0-1033.37~18.04.1","5.4.0-1034.38~18.04.1","5.4.0-1036.41~18.04.1","5.4.0-1037.42~18.04.1","5.4.0-1040.45~18.04.2","5.4.0-1041.46~18.04.1","5.4.0-1042.47~18.04.1","5.4.0-1044.49~18.04.1","5.4.0-1045.50~18.04.1","5.4.0-1046.51~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1049.54~18.04.1","5.4.0-1050.55~18.04.1","5.4.0-1051.56~18.04.1","5.4.0-1052.57~18.04.1","5.4.0-1053.58~18.04.1","5.4.0-1054.59~18.04.1","5.4.0-1056.61~18.04.1","5.4.0-1057.62~18.04.1","5.4.0-1058.63~18.04.1","5.4.0-1059.64~18.04.1","5.4.0-1060.65~18.04.1","5.4.0-1061.66~18.04.1","5.4.0-1063.68~18.04.1","5.4.0-1064.69~18.04.1","5.4.0-1065.70~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1068.73~18.04.1","5.4.0-1069.74~18.04.1","5.4.0-1070.75~18.04.1","5.4.0-1071.76~18.04.1","5.4.0-1072.77~18.04.1","5.4.0-1073.78~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1075.80~18.04.1","5.4.0-1076.81~18.04.1","5.4.0-1077.82~18.04.1","5.4.0-1078.83~18.04.1","5.4.0-1079.84~18.04.1","5.4.0-1080.85~18.04.1","5.4.0-1081.86~18.04.1","5.4.0-1082.87~18.04.1","5.4.0-1083.88~18.04.1","5.4.0-1084.89~18.04.1","5.4.0-1085.90~18.04.1","5.4.0-1086.91~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1092.97~18.04.1","5.4.0-1093.98~18.04.1","5.4.0-1094.99~18.04.1","5.4.0-1095.100~18.04.1","5.4.0-1096.101~18.04.1","5.4.0-1097.102~18.04.1","5.4.0-1098.103~18.04.1","5.4.0-1099.104~18.04.1","5.4.0-1100.105~18.04.1","5.4.0-1102.107~18.04.1","5.4.0-1103.108~18.04.1","5.4.0-1104.109~18.04.1","5.4.0-1105.110~18.04.1","5.4.0-1107.112~18.04.1","5.4.0-1108.113~18.04.1","5.4.0-1109.114~18.04.1","5.4.0-1111.116~18.04.1","5.4.0-1112.117~18.04.1","5.4.0-1113.118~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1012.12","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1026.26","4.15.0-1027.27","4.15.0-1028.28","4.15.0-1029.29","4.15.0-1030.30","4.15.0-1031.31","4.15.0-1032.32","4.15.0-1034.34","4.15.0-1035.35","4.15.0-1036.36","4.15.0-1038.38","4.15.0-1039.39","4.15.0-1042.42","4.15.0-1043.43","4.15.0-1044.44","4.15.0-1046.46","4.15.0-1047.47","4.15.0-1048.48","4.15.0-1050.50","4.15.0-1051.51","4.15.0-1052.52","4.15.0-1053.53","4.15.0-1056.57","4.15.0-1058.59","4.15.0-1059.60","4.15.0-1060.61","4.15.0-1067.68","4.15.0-1069.70","4.15.0-1071.72","4.15.0-1072.73","4.15.0-1074.75","4.15.0-1075.76","4.15.0-1077.79","4.15.0-1079.81","4.15.0-1081.83","4.15.0-1082.84","4.15.0-1084.86","4.15.0-1085.87","4.15.0-1086.88","4.15.0-1087.89","4.15.0-1088.90","4.15.0-1089.91","4.15.0-1090.92","4.15.0-1091.93","4.15.0-1092.94","4.15.0-1094.96","4.15.0-1097.99","4.15.0-1098.100","4.15.0-1099.101","4.15.0-1100.102","4.15.0-1101.103","4.15.0-1102.104","4.15.0-1103.105","4.15.0-1105.107","4.15.0-1106.108","4.15.0-1107.109","4.15.0-1109.112","4.15.0-1110.113","4.15.0-1112.115","4.15.0-1113.116","4.15.0-1114.117","4.15.0-1116.119","4.15.0-1119.123","4.15.0-1122.127","4.15.0-1123.128","4.15.0-1125.130","4.15.0-1126.131","4.15.0-1127.132","4.15.0-1128.133","4.15.0-1129.134","4.15.0-1132.137","4.15.0-1133.138","4.15.0-1134.139","4.15.0-1135.140","4.15.0-1136.141","4.15.0-1137.142","4.15.0-1138.143","4.15.0-1139.144","4.15.0-1140.145","4.15.0-1141.146","4.15.0-1142.147","4.15.0-1143.148","4.15.0-1144.149","4.15.0-1145.150","4.15.0-1146.151","4.15.0-1147.152","4.15.0-1148.153","4.15.0-1149.154","4.15.0-1150.155","4.15.0-1151.156","4.15.0-1152.157","4.15.0-1153.158","4.15.0-1154.159","4.15.0-1155.160","4.15.0-1156.161","4.15.0-1157.162","4.15.0-1158.163","4.15.0-1159.164","4.15.0-1160.165","4.15.0-1161.166","4.15.0-1162.167","4.15.0-1163.168","4.15.0-1164.169","4.15.0-1165.170","4.15.0-1166.171","4.15.0-1167.172","4.15.0-1168.173","4.15.0-1169.174","4.15.0-1170.175","4.15.0-1171.176","4.15.0-1172.177","4.15.0-1173.178","4.15.0-1174.179","4.15.0-1175.180","4.15.0-1176.181","4.15.0-1177.182","4.15.0-1178.183","4.15.0-1179.184","4.15.0-1180.185","4.15.0-1181.186"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9","4.15.0-1008.10","4.15.0-1009.11","4.15.0-1010.12","4.15.0-1011.13","4.15.0-1013.15","4.15.0-1014.16","4.15.0-1015.17","4.15.0-1017.19","4.15.0-1018.20","4.15.0-1021.23","4.15.0-1022.25","4.15.0-1023.26","4.15.0-1025.28","4.15.0-1026.29","4.15.0-1027.30","4.15.0-1029.32","4.15.0-1030.33","4.15.0-1031.34","4.15.0-1033.36","4.15.0-1035.39","4.15.0-1037.41","4.15.0-1038.42","4.15.0-1039.43","4.15.0-1045.49","4.15.0-1047.51","4.15.0-1048.52","4.15.0-1050.54","4.15.0-1051.55","4.15.0-1053.57","4.15.0-1054.58","4.15.0-1057.62","4.15.0-1058.64","4.15.0-1059.65","4.15.0-1061.67","4.15.0-1062.68","4.15.0-1063.70","4.15.0-1064.71","4.15.0-1065.73","4.15.0-1066.74","4.15.0-1067.75","4.15.0-1068.76","4.15.0-1069.77","4.15.0-1070.78","4.15.0-1071.79","4.15.0-1072.80","4.15.0-1075.83","4.15.0-1078.86","4.15.0-1079.87","4.15.0-1080.88","4.15.0-1081.89","4.15.0-1082.90","4.15.0-1083.91","4.15.0-1084.92","4.15.0-1085.93","4.15.0-1086.94","4.15.0-1087.95","4.15.0-1089.98","4.15.0-1090.99","4.15.0-1091.100","4.15.0-1092.101","4.15.0-1093.102","4.15.0-1095.104","4.15.0-1098.108","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1106.117","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1120.131","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.153","4.15.0-1143.154","4.15.0-1144.155","4.15.0-1145.156","4.15.0-1146.157","4.15.0-1147.158","4.15.0-1148.159","4.15.0-1149.160","4.15.0-1150.161","4.15.0-1151.162","4.15.0-1152.163","4.15.0-1153.164","4.15.0-1154.165","4.15.0-1155.166","4.15.0-1156.167","4.15.0-1158.169","4.15.0-1160.171","4.15.0-1161.172"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-oracle-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1019.19~18.04.1","5.4.0-1021.21~18.04.1","5.4.0-1022.22~18.04.1","5.4.0-1024.24~18.04.1","5.4.0-1025.25~18.04.1","5.4.0-1028.29~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1033.35","5.4.0-1034.36~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1037.40~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1039.42~18.04.1","5.4.0-1041.44~18.04.1","5.4.0-1042.45~18.04.1","5.4.0-1043.46~18.04.1","5.4.0-1044.47~18.04.1","5.4.0-1046.50~18.04.2","5.4.0-1048.52~18.04.1","5.4.0-1049.53~18.04.1","5.4.0-1052.56~18.04.1","5.4.0-1053.57~18.04.1","5.4.0-1054.58~18.04.1","5.4.0-1055.59~18.04.1","5.4.0-1056.60~18.04.1","5.4.0-1057.61~18.04.1","5.4.0-1058.62~18.04.1","5.4.0-1059.63~18.04.1","5.4.0-1061.65~18.04.1","5.4.0-1062.66~18.04.1","5.4.0-1063.67~18.04.1","5.4.0-1064.68~18.04.1","5.4.0-1066.71~18.04.1","5.4.0-1067.72~18.04.1","5.4.0-1069.75~18.04.1","5.4.0-1070.76~18.04.1","5.4.0-1071.77~18.04.1","5.4.0-1073.79~18.04.1","5.4.0-1076.83~18.04.1","5.4.0-1078.86~18.04.1","5.4.0-1079.87~18.04.1","5.4.0-1081.89~18.04.1","5.4.0-1082.90~18.04.1","5.4.0-1083.91~18.04.1","5.4.0-1084.92~18.04.1","5.4.0-1086.95~18.04.1","5.4.0-1087.96~18.04.1","5.4.0-1090.99~18.04.2","5.4.0-1091.100~18.04.1","5.4.0-1092.101~18.04.1","5.4.0-1093.102~18.04.1","5.4.0-1094.103~18.04.1","5.4.0-1098.107~18.04.1","5.4.0-1099.108~18.04.1","5.4.0-1100.109~18.04.1","5.4.0-1101.110~18.04.1","5.4.0-1102.111~18.04.1","5.4.0-1103.112~18.04.1","5.4.0-1104.113~18.04.1","5.4.0-1105.114~18.04.1","5.4.0-1106.115~18.04.1","5.4.0-1107.116~18.04.1","5.4.0-1108.117~18.04.1","5.4.0-1109.118~18.04.1","5.4.0-1110.119~18.04.1","5.4.0-1111.120~18.04.1","5.4.0-1112.121~18.04.4","5.4.0-1113.122~18.04.1","5.4.0-1115.124~18.04.1","5.4.0-1116.125~18.04.1","5.4.0-1117.126~18.04.1","5.4.0-1118.127~18.04.1","5.4.0-1119.128~18.04.1","5.4.0-1120.129~18.04.1","5.4.0-1121.130~18.04.1","5.4.0-1122.131~18.04.1","5.4.0-1123.132~18.04.1","5.4.0-1124.133~18.04.1","5.4.0-1125.134~18.04.1","5.4.0-1126.135~18.04.1","5.4.0-1127.136~18.04.1","5.4.0-1129.138~18.04.1","5.4.0-1130.139~18.04.1","5.4.0-1131.140~18.04.1","5.4.0-1132.141~18.04.1","5.4.0-1133.142~18.04.1","5.4.0-1134.143~18.04.1","5.4.0-1135.144~18.04.1","5.4.0-1136.145~18.04.1","5.4.0-1137.146~18.04.1","5.4.0-1138.147~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.151~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1143.153~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1155.165~18.04.1","5.4.0-1156.166~18.04.2","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1159.169~18.04.1","5.4.0-1161.171~18.04.1","5.4.0-1162.172~18.04.1","5.4.0-1163.173~18.04.1","5.4.0-1164.174~18.04.1","5.4.0-1165.175~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1013.13~18.04.1","5.4.0-1015.15~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.20~18.04.1","5.4.0-1019.21~18.04.1","5.4.0-1021.24~18.04.1","5.4.0-1022.25~18.04.1","5.4.0-1023.26~18.04.1","5.4.0-1025.28~18.04.1","5.4.0-1026.29~18.04.1","5.4.0-1028.31~18.04.1","5.4.0-1029.32~18.04.1","5.4.0-1030.33~18.04.1","5.4.0-1032.35~18.04.1","5.4.0-1033.36~18.04.1","5.4.0-1034.37~18.04.1","5.4.0-1035.38~18.04.1","5.4.0-1036.39~18.04.1","5.4.0-1038.41~18.04.1","5.4.0-1041.45~18.04.1","5.4.0-1042.46~18.04.3","5.4.0-1043.47~18.04.1","5.4.0-1044.48~18.04.1","5.4.0-1045.49~18.04.1","5.4.0-1046.50~18.04.1","5.4.0-1047.52~18.04.1","5.4.0-1048.53~18.04.1","5.4.0-1050.56~18.04.1","5.4.0-1052.58~18.04.1","5.4.0-1053.60~18.04.1","5.4.0-1055.62~18.04.1","5.4.0-1056.63~18.04.1","5.4.0-1058.65~18.04.1","5.4.0-1059.66~18.04.1","5.4.0-1060.68~18.04.1","5.4.0-1062.70~18.04.1","5.4.0-1065.75~18.04.1","5.4.0-1066.76~18.04.1","5.4.0-1068.78~18.04.1","5.4.0-1069.79~18.04.1","5.4.0-1070.80~18.04.1","5.4.0-1071.81~18.04.1","5.4.0-1073.84~18.04.1","5.4.0-1074.85~18.04.1","5.4.0-1077.88~18.04.2","5.4.0-1078.89~18.04.1","5.4.0-1079.90~18.04.1","5.4.0-1080.91~18.04.1","5.4.0-1081.92~18.04.1","5.4.0-1082.93~18.04.1","5.4.0-1083.94~18.04.1","5.4.0-1084.95~18.04.1","5.4.0-1085.96~18.04.1","5.4.0-1086.97~18.04.1","5.4.0-1088.99~18.04.1","5.4.0-1089.100~18.04.1","5.4.0-1090.101~18.04.1","5.4.0-1091.102~18.04.1","5.4.0-1092.103~18.04.1","5.4.0-1093.104~18.04.1","5.4.0-1094.105~18.04.1","5.4.0-1095.106~18.04.1","5.4.0-1096.107~18.04.1","5.4.0-1097.109~18.04.2","5.4.0-1098.110~18.04.2","5.4.0-1100.112~18.04.1","5.4.0-1101.113~18.04.1","5.4.0-1102.114~18.04.1","5.4.0-1103.115~18.04.1","5.4.0-1104.116~18.04.1","5.4.0-1105.117~18.04.1","5.4.0-1106.118~18.04.1","5.4.0-1107.119~18.04.1","5.4.0-1108.120~18.04.1","5.4.0-1109.121~18.04.1","5.4.0-1110.122~18.04.1","5.4.0-1111.123~18.04.1","5.4.0-1112.124~18.04.1","5.4.0-1114.126~18.04.1","5.4.0-1115.127~18.04.1","5.4.0-1116.128~18.04.1","5.4.0-1117.129~18.04.1","5.4.0-1118.130~18.04.1","5.4.0-1119.131~18.04.1","5.4.0-1120.132~18.04.1","5.4.0-1121.133~18.04.1","5.4.0-1122.134~18.04.1","5.4.0-1129.142~18.04.1","5.4.0-1130.143~18.04.1","5.4.0-1131.144~18.04.1","5.4.0-1132.145~18.04.1","5.4.0-1133.146~18.04.1","5.4.0-1134.147~18.04.1","5.4.0-1135.148~18.04.1","5.4.0-1136.149~18.04.1","5.4.0-1137.150~18.04.1","5.4.0-1139.152~18.04.1","5.4.0-1140.153~18.04.1","5.4.0-1143.156~18.04.1","5.4.0-1144.157~18.04.1","5.4.0-1145.158~18.04.1","5.4.0-1146.159~18.04.1","5.4.0-1147.160~18.04.1","5.4.0-1148.161~18.04.1","5.4.0-1149.162~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4","4.15.0-2018.18","4.15.0-2021.21","4.15.0-2022.22","4.15.0-2024.24","4.15.0-2025.25","4.15.0-2026.26","4.15.0-2027.27","4.15.0-2030.31","4.15.0-2031.32","4.15.0-2033.34","4.15.0-2034.35","4.15.0-2035.37","4.15.0-2036.38","4.15.0-2037.39","4.15.0-2038.40","4.15.0-2039.41","4.15.0-2040.42","4.15.0-2041.43","4.15.0-2042.44","4.15.0-2044.46","4.15.0-2045.47","4.15.0-2048.50","4.15.0-2051.53","4.15.0-2052.54","4.15.0-2053.55","4.15.0-2054.56","4.15.0-2055.57","4.15.0-2056.58","4.15.0-2057.59","4.15.0-2059.61","4.15.0-2060.62","4.15.0-2061.63","4.15.0-2063.66","4.15.0-2064.67","4.15.0-2065.68","4.15.0-2066.69","4.15.0-2067.70","4.15.0-2069.72","4.15.0-2072.76","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2078.83","4.15.0-2079.84","4.15.0-2080.85","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2085.91","4.15.0-2087.93","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2103.109","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2107.113","4.15.0-2108.114","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123","4.15.0-2118.124","4.15.0-2119.125","4.15.0-2120.126","4.15.0-2121.127","4.15.0-2122.128","4.15.0-2123.129","4.15.0-2124.130","4.15.0-2125.131","4.15.0-2126.132","4.15.0-2127.133","4.15.0-2128.134","4.15.0-2129.135","4.15.0-2130.136","4.15.0-2132.138","4.15.0-2133.139","4.15.0-2134.140","4.15.0-2135.141","4.15.0-2136.142","4.15.0-2137.143"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-2006.7","4.15.0-2007.8","4.15.0-2008.9","4.15.0-2009.10","4.15.0-2012.14","4.15.0-2013.15","4.15.0-2015.17","4.15.0-2016.18","4.15.0-2017.20","4.15.0-2018.21","4.15.0-2020.23","4.15.0-2021.24","4.15.0-2022.25","4.15.0-2023.26","4.15.0-2024.27","4.15.0-2025.28","4.15.0-2026.29","4.15.0-2027.30","4.15.0-2030.33","4.15.0-2033.37","4.15.0-2034.38","4.15.0-2035.39","4.15.0-2036.40","4.15.0-2037.41","4.15.0-2038.42","4.15.0-2039.43","4.15.0-2041.45","4.15.0-2042.46","4.15.0-2043.47","4.15.0-2045.49","4.15.0-2046.50","4.15.0-2047.51","4.15.0-2048.52","4.15.0-2049.53","4.15.0-2050.54","4.15.0-2053.58","4.15.0-2056.62","4.15.0-2057.63","4.15.0-2059.65","4.15.0-2060.66","4.15.0-2062.68","4.15.0-2066.72","4.15.0-2067.73","4.15.0-2068.74","4.15.0-2070.76","4.15.0-2071.77","4.15.0-2072.78","4.15.0-2073.79","4.15.0-2074.80","4.15.0-2075.81","4.15.0-2076.82","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106","4.15.0-2101.107","4.15.0-2102.108","4.15.0-2104.110","4.15.0-2105.111","4.15.0-2106.112","4.15.0-2109.115","4.15.0-2110.116","4.15.0-2111.117","4.15.0-2112.118","4.15.0-2113.119","4.15.0-2114.120","4.15.0-2115.121","4.15.0-2116.122","4.15.0-2117.123"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1027.32","4.15.0-1029.34","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1037.42","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1040.45","4.15.0-1041.46","4.15.0-1044.50","4.15.0-1045.52","4.15.0-1046.53","4.15.0-1048.55","4.15.0-1049.56","4.15.0-1050.58","4.15.0-1051.59","4.15.0-1052.60","4.15.0-1053.61","4.15.0-1054.62","4.15.0-1055.63","4.15.0-1056.64","4.15.0-1057.65","4.15.0-1058.66","4.15.0-1059.67","4.15.0-1060.68","4.15.0-1063.71","4.15.0-1066.75","4.15.0-1067.76","4.15.0-1068.77","4.15.0-1069.78","4.15.0-1070.79","4.15.0-1071.80","4.15.0-1072.81","4.15.0-1073.82","4.15.0-1075.84","4.15.0-1076.85","4.15.0-1078.87","4.15.0-1080.89","4.15.0-1081.90","4.15.0-1083.92","4.15.0-1084.93","4.15.0-1085.94","4.15.0-1087.96","4.15.0-1090.100","4.15.0-1093.104","4.15.0-1094.105","4.15.0-1096.107","4.15.0-1097.108","4.15.0-1098.109","4.15.0-1099.110","4.15.0-1100.111","4.15.0-1103.114","4.15.0-1104.115","4.15.0-1105.116","4.15.0-1107.118","4.15.0-1108.119","4.15.0-1109.120","4.15.0-1110.121","4.15.0-1111.122","4.15.0-1112.123","4.15.0-1113.124","4.15.0-1114.125","4.15.0-1115.126","4.15.0-1116.127","4.15.0-1117.128","4.15.0-1118.129","4.15.0-1119.130","4.15.0-1121.132","4.15.0-1122.133","4.15.0-1123.134","4.15.0-1124.135","4.15.0-1125.136","4.15.0-1126.137","4.15.0-1127.138","4.15.0-1128.139","4.15.0-1129.140","4.15.0-1130.141","4.15.0-1131.142","4.15.0-1132.143","4.15.0-1133.144","4.15.0-1134.145","4.15.0-1135.146","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1138.149","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.153","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1145.157","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1149.161","4.15.0-1150.162","4.15.0-1151.163","4.15.0-1152.164","4.15.0-1153.165","4.15.0-1154.166"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2013.14","4.15.0-2016.18","4.15.0-2017.19","4.15.0-2018.20","4.15.0-2019.21","4.15.0-2020.22","4.15.0-2021.23","4.15.0-2022.24","4.15.0-2024.26","4.15.0-2025.27","4.15.0-2026.28","4.15.0-2028.31","4.15.0-2029.32","4.15.0-2030.33","4.15.0-2031.34","4.15.0-2032.35","4.15.0-2034.37","4.15.0-2037.41","4.15.0-2040.45","4.15.0-2041.46","4.15.0-2043.48","4.15.0-2044.49","4.15.0-2045.50","4.15.0-2047.52","4.15.0-2050.55","4.15.0-2052.57","4.15.0-2054.59","4.15.0-2055.60","4.15.0-2056.61","4.15.0-2057.62","4.15.0-2058.63","4.15.0-2059.64","4.15.0-2060.65","4.15.0-2061.66","4.15.0-2062.67","4.15.0-2063.68","4.15.0-2064.69","4.15.0-2065.70","4.15.0-2066.71","4.15.0-2067.72","4.15.0-2068.73","4.15.0-2069.74","4.15.0-2070.75","4.15.0-2071.76","4.15.0-2072.77","4.15.0-2073.78","4.15.0-2074.79","4.15.0-2075.80","4.15.0-2076.81","4.15.0-2077.83","4.15.0-2078.84","4.15.0-2079.85","4.15.0-2080.86","4.15.0-2081.87","4.15.0-2082.88","4.15.0-2083.89","4.15.0-2084.90","4.15.0-2085.91","4.15.0-2086.92","4.15.0-2087.93","4.15.0-2088.94","4.15.0-2089.95","4.15.0-2090.96","4.15.0-2091.97","4.15.0-2092.98","4.15.0-2093.99","4.15.0-2094.100","4.15.0-2095.101","4.15.0-2096.102","4.15.0-2097.103","4.15.0-2098.104","4.15.0-2099.105","4.15.0-2100.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-2000.4"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1011.12"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:18.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-18.19","5.3.0-24.26","5.4.0-9.12","5.4.0-18.22","5.4.0-21.25","5.4.0-24.28","5.4.0-25.29","5.4.0-26.30","5.4.0-28.32","5.4.0-29.33","5.4.0-31.35","5.4.0-33.37","5.4.0-37.41","5.4.0-39.43","5.4.0-40.44","5.4.0-42.46","5.4.0-45.49","5.4.0-47.51","5.4.0-48.52","5.4.0-51.56","5.4.0-52.57","5.4.0-53.59","5.4.0-54.60","5.4.0-56.62","5.4.0-58.64","5.4.0-59.65","5.4.0-60.67","5.4.0-62.70","5.4.0-64.72","5.4.0-65.73","5.4.0-66.74","5.4.0-67.75","5.4.0-70.78","5.4.0-71.79","5.4.0-72.80","5.4.0-73.82","5.4.0-74.83","5.4.0-77.86","5.4.0-80.90","5.4.0-81.91","5.4.0-84.94","5.4.0-86.97","5.4.0-88.99","5.4.0-89.100","5.4.0-90.101","5.4.0-91.102","5.4.0-92.103","5.4.0-94.106","5.4.0-96.109","5.4.0-97.110","5.4.0-99.112","5.4.0-100.113","5.4.0-104.118","5.4.0-105.119","5.4.0-107.121","5.4.0-109.123","5.4.0-110.124","5.4.0-113.127","5.4.0-117.132","5.4.0-120.136","5.4.0-121.137","5.4.0-122.138","5.4.0-124.140","5.4.0-125.141","5.4.0-126.142","5.4.0-128.144","5.4.0-131.147","5.4.0-132.148","5.4.0-135.152","5.4.0-136.153","5.4.0-137.154","5.4.0-139.156","5.4.0-144.161","5.4.0-146.163","5.4.0-147.164","5.4.0-148.165","5.4.0-149.166","5.4.0-150.167","5.4.0-152.169","5.4.0-153.170","5.4.0-155.172","5.4.0-156.173","5.4.0-159.176","5.4.0-162.179","5.4.0-163.180","5.4.0-164.181","5.4.0-165.182","5.4.0-166.183","5.4.0-167.184","5.4.0-169.187","5.4.0-170.188","5.4.0-171.189","5.4.0-172.190","5.4.0-173.191","5.4.0-174.193","5.4.0-176.196","5.4.0-177.197","5.4.0-181.201","5.4.0-182.202","5.4.0-186.206","5.4.0-187.207","5.4.0-189.209","5.4.0-190.210","5.4.0-192.212","5.4.0-193.213","5.4.0-195.215","5.4.0-196.216","5.4.0-198.218","5.4.0-200.220","5.4.0-202.222","5.4.0-204.224","5.4.0-205.225","5.4.0-208.228","5.4.0-211.231","5.4.0-212.232","5.4.0-214.234","5.4.0-215.235","5.4.0-216.236","5.4.0-218.238","5.4.0-219.239","5.4.0-220.240","5.4.0-221.241","5.4.0-222.242","5.4.0-223.243","5.4.0-224.244","5.4.0-225.245","5.4.0-227.247","5.4.0-228.248","5.4.0-229.249","5.4.0-230.250","5.4.0-231.251","5.4.0-233.253","5.4.0-234.254","5.4.0-238.258","5.4.0-241.261","5.4.0-242.262","5.4.0-244.264","5.4.0-245.265"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.3.0-1010.11","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1017.17","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.37","5.4.0-1037.39","5.4.0-1038.40","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1045.47","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1088.96","5.4.0-1089.97","5.4.0-1092.100","5.4.0-1093.101","5.4.0-1094.102","5.4.0-1096.104","5.4.0-1097.105","5.4.0-1099.107","5.4.0-1100.108","5.4.0-1101.109","5.4.0-1102.110","5.4.0-1103.111","5.4.0-1104.112","5.4.0-1105.113","5.4.0-1106.114","5.4.0-1107.115","5.4.0-1108.116","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.123","5.4.0-1114.124","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1129.139","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1142.152","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1148.158","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1153.163","5.4.0-1154.164","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.172","5.4.0-1162.173","5.4.0-1163.174","5.4.0-1164.175","5.4.0-1165.176","5.4.0-1166.177","5.4.0-1167.178"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119","5.4.0-1114.120","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1122.129","5.4.0-1123.130","5.4.0-1124.131","5.4.0-1126.133","5.4.0-1127.134","5.4.0-1128.135","5.4.0-1129.136","5.4.0-1130.137","5.4.0-1131.138","5.4.0-1132.139","5.4.0-1133.140","5.4.0-1134.141","5.4.0-1135.142","5.4.0-1136.143","5.4.0-1137.144","5.4.0-1138.145","5.4.0-1139.146","5.4.0-1140.147","5.4.0-1142.149","5.4.0-1143.150","5.4.0-1145.152","5.4.0-1147.154","5.4.0-1148.155","5.4.0-1149.156","5.4.0-1150.157","5.4.0-1151.158","5.4.0-1152.159","5.4.0-1153.160","5.4.0-1154.161","5.4.0-1156.163","5.4.0-1157.164","5.4.0-1160.166","5.4.0-1161.167","5.4.0-1162.168","5.4.0-1163.169","5.4.0-1164.170","5.4.0-1166.172","5.4.0-1167.173","5.4.0-1168.174","5.4.0-1169.175","5.4.0-1170.176","5.4.0-1171.177","5.4.0-1172.178"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.10","5.4.0-1011.14","5.4.0-1012.15","5.4.0-1013.16","5.4.0-1016.19","5.4.0-1019.22","5.4.0-1020.23","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1040.44","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1049.55","5.4.0-1050.56","5.4.0-1054.60","5.4.0-1058.64","5.4.0-1059.65","5.4.0-1060.66","5.4.0-1062.68","5.4.0-1064.70","5.4.0-1065.71","5.4.0-1066.72","5.4.0-1068.74","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1072.78","5.4.0-1073.79","5.4.0-1074.80","5.4.0-1075.81","5.4.0-1076.82","5.4.0-1077.83","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1080.87","5.4.0-1081.88","5.4.0-1082.89","5.4.0-1083.90","5.4.0-1084.91","5.4.0-1085.92","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1088.95","5.4.0-1089.96","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1092.99","5.4.0-1093.100","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.126","5.4.0-1120.127","5.4.0-1121.128","5.4.0-1123.130","5.4.0-1125.132","5.4.0-1126.133"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1004.4","5.3.0-1009.10","5.3.0-1011.12","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1033.35","5.4.0-1034.37","5.4.0-1036.39","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1040.43","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1044.47","5.4.0-1046.49","5.4.0-1049.53","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1060.64","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1075.80","5.4.0-1078.84","5.4.0-1080.87","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.94","5.4.0-1087.95","5.4.0-1089.97","5.4.0-1090.98","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1096.105","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1128.137","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1142.151","5.4.0-1143.152","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163","5.4.0-1155.164","5.4.0-1156.165","5.4.0-1157.166","5.4.0-1159.168","5.4.0-1160.169","5.4.0-1161.170","5.4.0-1162.171","5.4.0-1163.172","5.4.0-1164.173","5.4.0-1165.174","5.4.0-1166.175","5.4.0-1167.177","5.4.0-1168.178","5.4.0-1169.179","5.4.0-1170.180"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1003.4","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1006.7","5.4.0-1007.8","5.4.0-1008.9","5.4.0-1010.11","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1017.19","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1020.22","5.4.0-1021.23","5.4.0-1023.25","5.4.0-1026.29","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1036.41","5.4.0-1037.42","5.4.0-1040.45","5.4.0-1041.46","5.4.0-1042.47","5.4.0-1044.49","5.4.0-1045.50","5.4.0-1046.51","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1049.54","5.4.0-1050.55","5.4.0-1051.56","5.4.0-1052.57","5.4.0-1053.58","5.4.0-1054.59","5.4.0-1056.61","5.4.0-1057.62","5.4.0-1058.63","5.4.0-1059.64","5.4.0-1060.65","5.4.0-1061.66","5.4.0-1063.68","5.4.0-1064.69","5.4.0-1065.70","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1068.73","5.4.0-1069.74","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1077.82","5.4.0-1078.83","5.4.0-1079.84","5.4.0-1080.85","5.4.0-1081.86","5.4.0-1082.87","5.4.0-1083.88","5.4.0-1084.89","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1088.93","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1092.97","5.4.0-1093.98","5.4.0-1094.99","5.4.0-1095.100","5.4.0-1096.101","5.4.0-1097.102","5.4.0-1098.103","5.4.0-1099.104","5.4.0-1100.105","5.4.0-1102.107","5.4.0-1103.108","5.4.0-1104.109","5.4.0-1105.110","5.4.0-1107.112","5.4.0-1108.113","5.4.0-1109.114","5.4.0-1111.116","5.4.0-1112.117","5.4.0-1113.118"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.3","5.4.0-1004.6","5.4.0-1005.7","5.4.0-1006.8","5.4.0-1009.11","5.4.0-1010.12","5.4.0-1011.13","5.4.0-1012.14","5.4.0-1013.15","5.4.0-1014.16","5.4.0-1017.18","5.4.0-1018.19","5.4.0-1019.20","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1029.30","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1042.43","5.4.0-1043.44","5.4.0-1044.45","5.4.0-1045.46","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1060.63","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1071.74"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1004.4","5.4.0-1006.6","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1020.20","5.4.0-1021.21","5.4.0-1023.23","5.4.0-1024.24","5.4.0-1026.27","5.4.0-1028.29","5.4.0-1030.31","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1041.42","5.4.0-1044.46","5.4.0-1045.47","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1050.52","5.4.0-1051.53","5.4.0-1053.55","5.4.0-1054.56","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.61","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1068.72","5.4.0-1070.75","5.4.0-1071.76","5.4.0-1073.78","5.4.0-1074.79","5.4.0-1075.80","5.4.0-1076.81","5.4.0-1078.84","5.4.0-1079.85","5.4.0-1082.88","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.92","5.4.0-1087.93","5.4.0-1088.94","5.4.0-1089.95","5.4.0-1090.96","5.4.0-1091.97","5.4.0-1092.98","5.4.0-1093.99","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1096.102","5.4.0-1097.103","5.4.0-1098.104","5.4.0-1099.105","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1102.108","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112","5.4.0-1106.113","5.4.0-1107.114","5.4.0-1108.115","5.4.0-1109.116","5.4.0-1110.117","5.4.0-1111.118","5.4.0-1112.119","5.4.0-1113.120","5.4.0-1114.121","5.4.0-1115.122","5.4.0-1116.123","5.4.0-1117.124","5.4.0-1118.125","5.4.0-1119.127","5.4.0-1120.128","5.4.0-1121.129","5.4.0-1122.130","5.4.0-1123.131","5.4.0-1124.132","5.4.0-1125.133","5.4.0-1126.134","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1143.152","5.4.0-1144.153","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55~20.04.1"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1002.2","5.3.0-1007.8","5.3.0-1008.9","5.4.0-1005.5","5.4.0-1007.7","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1011.11","5.4.0-1015.15","5.4.0-1018.18","5.4.0-1019.19","5.4.0-1021.21","5.4.0-1022.22","5.4.0-1024.24","5.4.0-1025.25","5.4.0-1028.29","5.4.0-1029.31","5.4.0-1030.32","5.4.0-1032.34","5.4.0-1034.36","5.4.0-1035.38","5.4.0-1037.40","5.4.0-1038.41","5.4.0-1039.42","5.4.0-1041.44","5.4.0-1042.45","5.4.0-1043.46","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1058.62","5.4.0-1059.63","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1063.67","5.4.0-1064.68","5.4.0-1066.71","5.4.0-1067.72","5.4.0-1069.75","5.4.0-1070.76","5.4.0-1071.77","5.4.0-1073.79","5.4.0-1076.83","5.4.0-1078.86","5.4.0-1079.87","5.4.0-1081.89","5.4.0-1082.90","5.4.0-1083.91","5.4.0-1084.92","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1090.99","5.4.0-1091.100","5.4.0-1092.101","5.4.0-1093.102","5.4.0-1094.103","5.4.0-1097.106","5.4.0-1098.107","5.4.0-1099.108","5.4.0-1100.109","5.4.0-1101.110","5.4.0-1102.111","5.4.0-1103.112","5.4.0-1104.113","5.4.0-1105.114","5.4.0-1106.115","5.4.0-1107.116","5.4.0-1108.117","5.4.0-1109.118","5.4.0-1110.119","5.4.0-1111.120","5.4.0-1112.121","5.4.0-1113.122","5.4.0-1115.124","5.4.0-1116.125","5.4.0-1117.126","5.4.0-1118.127","5.4.0-1119.128","5.4.0-1120.129","5.4.0-1121.130","5.4.0-1122.131","5.4.0-1123.132","5.4.0-1124.133","5.4.0-1125.134","5.4.0-1126.135","5.4.0-1127.136","5.4.0-1129.138","5.4.0-1130.139","5.4.0-1131.140","5.4.0-1132.141","5.4.0-1133.142","5.4.0-1134.143","5.4.0-1135.144","5.4.0-1136.145","5.4.0-1137.146","5.4.0-1138.147","5.4.0-1140.150","5.4.0-1141.151","5.4.0-1142.152","5.4.0-1143.153","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1154.164","5.4.0-1155.165","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.171","5.4.0-1162.172","5.4.0-1163.173","5.4.0-1164.174","5.4.0-1165.175"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.7","5.4.0-1008.8","5.4.0-1011.11","5.4.0-1012.12","5.4.0-1013.13","5.4.0-1015.15","5.4.0-1016.17","5.4.0-1018.20","5.4.0-1019.21","5.4.0-1021.24","5.4.0-1022.25","5.4.0-1023.26","5.4.0-1025.28","5.4.0-1026.29","5.4.0-1028.31","5.4.0-1029.32","5.4.0-1030.33","5.4.0-1032.35","5.4.0-1033.36","5.4.0-1034.37","5.4.0-1035.38","5.4.0-1036.39","5.4.0-1038.41","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.52","5.4.0-1048.53","5.4.0-1050.56","5.4.0-1052.58","5.4.0-1053.60","5.4.0-1055.62","5.4.0-1056.63","5.4.0-1058.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1062.70","5.4.0-1065.75","5.4.0-1066.76","5.4.0-1068.78","5.4.0-1069.79","5.4.0-1070.80","5.4.0-1071.81","5.4.0-1073.84","5.4.0-1074.85","5.4.0-1077.88","5.4.0-1078.89","5.4.0-1079.90","5.4.0-1080.91","5.4.0-1081.92","5.4.0-1082.93","5.4.0-1083.94","5.4.0-1084.95","5.4.0-1085.96","5.4.0-1086.97","5.4.0-1088.99","5.4.0-1089.100","5.4.0-1090.101","5.4.0-1091.102","5.4.0-1092.103","5.4.0-1093.104","5.4.0-1094.105","5.4.0-1095.106","5.4.0-1096.107","5.4.0-1097.109","5.4.0-1098.110","5.4.0-1100.112","5.4.0-1101.113","5.4.0-1102.114","5.4.0-1103.115","5.4.0-1104.116","5.4.0-1105.117","5.4.0-1106.118","5.4.0-1107.119","5.4.0-1108.120","5.4.0-1109.121","5.4.0-1110.122","5.4.0-1111.123","5.4.0-1112.124","5.4.0-1113.125","5.4.0-1114.126","5.4.0-1115.127","5.4.0-1116.128","5.4.0-1117.129","5.4.0-1118.130","5.4.0-1119.131","5.4.0-1120.132","5.4.0-1121.133","5.4.0-1122.134","5.4.0-1129.142","5.4.0-1130.143","5.4.0-1131.144","5.4.0-1132.145","5.4.0-1133.146","5.4.0-1134.147","5.4.0-1135.148","5.4.0-1136.149","5.4.0-1137.150","5.4.0-1139.152","5.4.0-1140.153","5.4.0-1143.156","5.4.0-1144.157","5.4.0-1145.158","5.4.0-1146.159","5.4.0-1147.160","5.4.0-1148.161","5.4.0-1149.162"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.101~20.04.1"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1020.24","5.4.0-1021.25","5.4.0-1022.26","5.4.0-1023.27","5.4.0-1024.28","5.4.0-1025.29","5.4.0-1026.30","5.4.0-1027.31","5.4.0-1028.32","5.4.0-1029.33","5.4.0-1030.34","5.4.0-1031.35","5.4.0-1032.36","5.4.0-1033.37","5.4.0-1034.38","5.4.0-1035.39","5.4.0-1036.40","5.4.0-1037.41","5.4.0-1038.42","5.4.0-1039.43","5.4.0-1040.44","5.4.0-1041.45","5.4.0-1042.46","5.4.0-1043.47","5.4.0-1044.48","5.4.0-1045.49","5.4.0-1046.50","5.4.0-1047.51","5.4.0-1048.52","5.4.0-1049.53","5.4.0-1050.54","5.4.0-1051.55","5.4.0-1052.56","5.4.0-1053.57","5.4.0-1054.58","5.4.0-1055.59","5.4.0-1056.60","5.4.0-1058.62","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1082.86","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2","5.4.0-1069.73+fips2","5.4.0-1071.76+fips1","5.4.0-1072.77+fips1","5.4.0-1073.78+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1083.90+fips1","5.4.0-1085.92+fips1","5.4.0-1086.93+fips1","5.4.0-1088.96+fips1","5.4.0-1089.97+fips1","5.4.0-1092.100+fips1","5.4.0-1093.101+fips1","5.4.0-1094.102+fips1","5.4.0-1096.104+fips1","5.4.0-1099.107+fips1","5.4.0-1100.108+fips1","5.4.0-1101.109+fips1","5.4.0-1102.110+fips1","5.4.0-1103.111+fips1","5.4.0-1104.112+fips1","5.4.0-1105.113+fips1","5.4.0-1106.114+fips1","5.4.0-1107.115+fips1","5.4.0-1108.116+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.123+fips1","5.4.0-1114.124+fips1","5.4.0-1116.126+fips1","5.4.0-1117.127+fips1","5.4.0-1118.128+fips1","5.4.0-1119.129+fips1","5.4.0-1120.130+fips1","5.4.0-1121.131+fips1","5.4.0-1122.132+fips1","5.4.0-1123.133+fips1","5.4.0-1124.134+fips1","5.4.0-1125.135+fips1","5.4.0-1126.136+fips2","5.4.0-1127.137+fips1","5.4.0-1128.138+fips1","5.4.0-1129.139+fips1","5.4.0-1130.140+fips1","5.4.0-1131.141+fips1","5.4.0-1132.142+fips1","5.4.0-1133.143+fips1","5.4.0-1134.144+fips1","5.4.0-1135.145+fips1","5.4.0-1136.146+fips1","5.4.0-1137.147+fips1","5.4.0-1139.149+fips1","5.4.0-1140.151+fips1","5.4.0-1142.153+fips1","5.4.0-1144.155+fips1","5.4.0-1145.156+fips1","5.4.0-1146.156+fips1","5.4.0-1147.157+fips1","5.4.0-1148.158+fips1","5.4.0-1149.159+fips1","5.4.0-1150.160+fips1","5.4.0-1151.161+fips1","5.4.0-1152.162+fips1","5.4.0-1153.163+fips1","5.4.0-1154.164+fips1","5.4.0-1155.165+fips1","5.4.0-1156.166+fips1","5.4.0-1157.167+fips1","5.4.0-1158.168+fips1","5.4.0-1159.169+fips1","5.4.0-1160.170+fips1","5.4.0-1161.172+fips1","5.4.0-1163.174+fips1","5.4.0-1165.176+fips1","5.4.0-1166.177+fips1","5.4.0-1167.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1","5.4.0-1073.76+fips1","5.4.0-1074.77+fips1","5.4.0-1076.79+fips1","5.4.0-1078.81+fips1","5.4.0-1080.83+fips1","5.4.0-1083.87+fips1","5.4.0-1085.90+fips1","5.4.0-1086.91+fips1","5.4.0-1089.94+fips1","5.4.0-1090.95+fips1","5.4.0-1091.96+fips1","5.4.0-1094.100+fips1","5.4.0-1095.101+fips1","5.4.0-1098.104+fips1","5.4.0-1100.106+fips1","5.4.0-1101.107+fips1","5.4.0-1103.109+fips1","5.4.0-1104.110+fips1","5.4.0-1105.111+fips1","5.4.0-1106.112+fips1","5.4.0-1107.113+fips1","5.4.0-1108.114+fips1","5.4.0-1109.115+fips1","5.4.0-1110.116+fips1","5.4.0-1111.117+fips1","5.4.0-1112.118+fips1","5.4.0-1113.119+fips1","5.4.0-1114.120+fips1","5.4.0-1115.122+fips1","5.4.0-1116.123+fips1","5.4.0-1117.124+fips1","5.4.0-1118.125+fips1","5.4.0-1119.126+fips1","5.4.0-1121.128+fips1","5.4.0-1122.129+fips1","5.4.0-1123.130+fips1","5.4.0-1124.131+fips1","5.4.0-1126.133+fips1","5.4.0-1127.134+fips1","5.4.0-1128.135+fips1","5.4.0-1129.136+fips1","5.4.0-1130.137+fips1","5.4.0-1131.138+fips1","5.4.0-1132.139+fips1","5.4.0-1133.140+fips1","5.4.0-1134.141+fips1","5.4.0-1135.142+fips1","5.4.0-1136.143+fips1","5.4.0-1137.144+fips1","5.4.0-1138.145+fips1","5.4.0-1139.146+fips1","5.4.0-1140.147+fips1","5.4.0-1142.149+fips1","5.4.0-1143.150+fips1","5.4.0-1145.152+fips1","5.4.0-1147.154+fips1","5.4.0-1148.156+fips1","5.4.0-1149.157+fips1","5.4.0-1151.158+fips1","5.4.0-1152.159+fips1","5.4.0-1153.160+fips1","5.4.0-1154.161+fips1","5.4.0-1155.162+fips1","5.4.0-1157.164+fips1","5.4.0-1158.165+fips1","5.4.0-1160.166+fips1","5.4.0-1161.167+fips1","5.4.0-1162.168+fips1","5.4.0-1163.169+fips1","5.4.0-1164.170+fips1","5.4.0-1166.172+fips1","5.4.0-1167.173+fips1","5.4.0-1168.174+fips1","5.4.0-1170.176+fips1","5.4.0-1171.177+fips1","5.4.0-1172.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1026.30","5.4.0-1028.32","5.4.0-1031.36","5.4.0-1032.37","5.4.0-1033.38","5.4.0-1034.40","5.4.0-1035.41","5.4.0-1036.42","5.4.0-1037.43","5.4.0-1038.44","5.4.0-1040.46","5.4.0-1041.47","5.4.0-1042.48","5.4.0-1043.49","5.4.0-1045.51","5.4.0-1046.52","5.4.0-1047.53","5.4.0-1048.54","5.4.0-1049.55","5.4.0-1051.57","5.4.0-1054.61","5.4.0-1056.64","5.4.0-1057.65","5.4.0-1059.67","5.4.0-1060.68","5.4.0-1061.69","5.4.0-1062.70","5.4.0-1064.73","5.4.0-1065.74","5.4.0-1068.77","5.4.0-1069.78","5.4.0-1070.79","5.4.0-1072.81","5.4.0-1073.82","5.4.0-1074.83","5.4.0-1075.84","5.4.0-1076.85","5.4.0-1077.86","5.4.0-1078.87","5.4.0-1079.88","5.4.0-1080.89","5.4.0-1081.90","5.4.0-1082.91","5.4.0-1083.92","5.4.0-1084.93","5.4.0-1085.94","5.4.0-1086.95","5.4.0-1087.96","5.4.0-1088.97","5.4.0-1089.98","5.4.0-1090.100","5.4.0-1091.101","5.4.0-1092.102","5.4.0-1094.104","5.4.0-1095.105","5.4.0-1096.106","5.4.0-1097.107","5.4.0-1098.108","5.4.0-1099.109","5.4.0-1100.110","5.4.0-1101.111","5.4.0-1102.112","5.4.0-1103.113","5.4.0-1104.114","5.4.0-1105.115","5.4.0-1106.116","5.4.0-1107.117","5.4.0-1108.118","5.4.0-1109.119","5.4.0-1110.120","5.4.0-1111.121","5.4.0-1112.122","5.4.0-1116.126","5.4.0-1117.127","5.4.0-1118.128","5.4.0-1119.129","5.4.0-1120.130","5.4.0-1121.131","5.4.0-1122.132","5.4.0-1123.133","5.4.0-1124.134","5.4.0-1125.135","5.4.0-1126.136","5.4.0-1127.137","5.4.0-1128.138","5.4.0-1130.140","5.4.0-1131.141","5.4.0-1132.142","5.4.0-1133.143","5.4.0-1134.144","5.4.0-1135.145","5.4.0-1136.146","5.4.0-1137.147","5.4.0-1138.148","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1141.151"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1","5.4.0-1067.71~20.04.1","5.4.0-1069.73+fips2","5.4.0-1071.75+fips1","5.4.0-1073.78+fips1","5.4.0-1075.80+fips1","5.4.0-1078.84+fips1","5.4.0-1080.87+fips1","5.4.0-1081.88+fips1","5.4.0-1086.94+fips1","5.4.0-1087.95+fips1","5.4.0-1089.97+fips1","5.4.0-1092.101+fips1","5.4.0-1093.102+fips1","5.4.0-1096.105+fips1","5.4.0-1097.106+fips1","5.4.0-1098.107+fips1","5.4.0-1100.109+fips1","5.4.0-1101.110+fips1","5.4.0-1102.111+fips1","5.4.0-1103.112+fips1","5.4.0-1104.113+fips1","5.4.0-1105.114+fips1","5.4.0-1106.115+fips1","5.4.0-1107.116+fips1","5.4.0-1108.117+fips1","5.4.0-1109.118+fips1","5.4.0-1110.119+fips1","5.4.0-1111.120+fips1","5.4.0-1112.121+fips1","5.4.0-1113.122+fips1","5.4.0-1115.124+fips1","5.4.0-1116.125+fips1","5.4.0-1117.126+fips1","5.4.0-1118.127+fips1","5.4.0-1120.129+fips1","5.4.0-1121.130+fips1","5.4.0-1122.131+fips1","5.4.0-1124.133+fips1","5.4.0-1125.134+fips1","5.4.0-1126.135+fips1","5.4.0-1127.136+fips1","5.4.0-1128.137+fips1","5.4.0-1129.138+fips1","5.4.0-1130.139+fips1","5.4.0-1131.140+fips1","5.4.0-1132.141+fips1","5.4.0-1133.142+fips1","5.4.0-1134.143+fips1","5.4.0-1135.144+fips1","5.4.0-1136.145+fips1","5.4.0-1137.146+fips1","5.4.0-1138.147+fips1","5.4.0-1139.148+fips1","5.4.0-1140.149+fips1","5.4.0-1141.150+fips1","5.4.0-1142.151+fips1","5.4.0-1143.152+fips1","5.4.0-1145.154+fips1","5.4.0-1146.155+fips1","5.4.0-1147.156+fips1","5.4.0-1148.157+fips1","5.4.0-1149.158+fips1","5.4.0-1150.159+fips1","5.4.0-1151.160+fips1","5.4.0-1152.161+fips1","5.4.0-1153.162+fips1","5.4.0-1154.163+fips1","5.4.0-1155.164+fips1","5.4.0-1156.165+fips1","5.4.0-1157.166+fips1","5.4.0-1159.168+fips1","5.4.0-1160.169+fips1","5.4.0-1161.170+fips1","5.4.0-1162.171+fips1","5.4.0-1163.172+fips1","5.4.0-1164.173+fips1","5.4.0-1165.174+fips1","5.4.0-1166.175+fips1","5.4.0-1167.176+fips1","5.4.0-1168.178+fips1","5.4.0-1169.179+fips1","5.4.0-1170.180+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1022.22+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1007.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1021.21+fips1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1057.60~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118.1"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1060.63~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.105"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.94"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-124.124~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.100"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.99"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.44"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.71"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.88"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.96"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.111"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1019.19~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"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"]},{"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"},{"fixed":"6.17.0-1021.21~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"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"]},{"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"},{"fixed":"6.17.0-1021.24~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"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"]},{"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"},{"fixed":"6.17.0-41.41~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"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"]},{"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"},{"fixed":"6.17.0-1031.31"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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"]},{"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"},{"fixed":"6.17.0-1030.30"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55"}]}],"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"]},{"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"},{"fixed":"6.17.0-1019.19~24.04.3"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"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"]},{"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-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.26"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"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"]},{"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"},{"fixed":"6.17.0-1018.20~24.04.1"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20","6.17.0-22.22","6.17.0-23.23","6.17.0-29.29","6.17.0-35.35","6.17.0-40.40"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1016.17","6.17.0-1018.19","6.17.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1016.16","6.17.0-1018.18"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1014.14","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10","6.17.0-1010.11","6.17.0-1011.12","6.17.0-1013.15","6.17.0-1014.16","6.17.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1","6.17.0-14.14.1","6.17.0-19.19.1","6.17.0-20.20.1","6.17.0-22.22.1","6.17.0-23.23.1","6.17.0-29.29.1","6.17.0-35.35.1","6.17.0-40.40.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100~20.04.1"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55~20.04.1"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.94"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.100"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.99"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.71"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110+fips1"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183+fips1"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112+fips1"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110~20.04.1"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112~20.04.1"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~20.04.1"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106~20.04.1"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.105"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.111"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.44"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.96"}]}],"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"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"],"bundled":334},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118+fips1"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"],"bundled":350},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"],"bundled":350},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~20.04.1"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1"],"bundled":426},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"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"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"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"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-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"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"],"bundled":218},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"],"bundled":393},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"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"],"bundled":516},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.24~24.04.1"}]}],"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"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.20~24.04.1"}]}],"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"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1019.19~24.04.3"}]}],"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"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1030.30"}]}],"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"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.21~24.04.1"}]}],"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"],"bundled":267},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.18~24.04.1"}]}],"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"],"bundled":266},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1031.31"}]}],"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"],"bundled":227},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/2b3329b3c29d9e188e40d902d5230c2d5989b940","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/5d0dc83cb9a69c1d0bea58f1c430199b05f6b021","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/4d3399c52e0e61720ae898f5a0b5b75d4460ae24","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/4ebc711b738d139cabe2fc9e7e7749847676a342","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/6f468f6ff233c6a81e0e761d9124e982903fe9a5","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/5647d42c47b535573b63e073e91164d6a5bb058c","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23047","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-484m-2c5w-2g38"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23047","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23047.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-23047","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0097.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35281","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.121","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.122","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.123","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.124","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.125","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.126","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.127","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.128","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.129","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.130","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0098.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35282","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23228","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1567","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1570","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261573-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1226591","tags":["report"]},{"url":"https://bugzilla.suse.com/1243208","tags":["report"]},{"url":"https://bugzilla.suse.com/1245728","tags":["report"]},{"url":"https://bugzilla.suse.com/1251135","tags":["report"]},{"url":"https://bugzilla.suse.com/1251971","tags":["report"]},{"url":"https://bugzilla.suse.com/1252073","tags":["report"]},{"url":"https://bugzilla.suse.com/1252266","tags":["report"]},{"url":"https://bugzilla.suse.com/1252803","tags":["report"]},{"url":"https://bugzilla.suse.com/1253049","tags":["report"]},{"url":"https://bugzilla.suse.com/1253129","tags":["report"]},{"url":"https://bugzilla.suse.com/1255687","tags":["report"]},{"url":"https://bugzilla.suse.com/1256504","tags":["report"]},{"url":"https://bugzilla.suse.com/1256647","tags":["report"]},{"url":"https://bugzilla.suse.com/1256690","tags":["report"]},{"url":"https://bugzilla.suse.com/1257466","tags":["report"]},{"url":"https://bugzilla.suse.com/1257472","tags":["report"]},{"url":"https://bugzilla.suse.com/1257506","tags":["report"]},{"url":"https://bugzilla.suse.com/1257561","tags":["report"]},{"url":"https://bugzilla.suse.com/1257682","tags":["report"]},{"url":"https://bugzilla.suse.com/1257773","tags":["report"]},{"url":"https://bugzilla.suse.com/1257777","tags":["report"]},{"url":"https://bugzilla.suse.com/1258280","tags":["report"]},{"url":"https://bugzilla.suse.com/1258303","tags":["report"]},{"url":"https://bugzilla.suse.com/1258305","tags":["report"]},{"url":"https://bugzilla.suse.com/1258330","tags":["report"]},{"url":"https://bugzilla.suse.com/1258337","tags":["report"]},{"url":"https://bugzilla.suse.com/1258414","tags":["report"]},{"url":"https://bugzilla.suse.com/1258424","tags":["report"]},{"url":"https://bugzilla.suse.com/1258447","tags":["report"]},{"url":"https://bugzilla.suse.com/1258476","tags":["report"]},{"url":"https://bugzilla.suse.com/1259188","tags":["report"]},{"url":"https://bugzilla.suse.com/1259580","tags":["report"]},{"url":"https://bugzilla.suse.com/1259707","tags":["report"]},{"url":"https://bugzilla.suse.com/1259795","tags":["report"]},{"url":"https://bugzilla.suse.com/1259797","tags":["report"]},{"url":"https://bugzilla.suse.com/1259865","tags":["report"]},{"url":"https://bugzilla.suse.com/1259866","tags":["report"]},{"url":"https://bugzilla.suse.com/1259886","tags":["report"]},{"url":"https://bugzilla.suse.com/1259889","tags":["report"]},{"url":"https://bugzilla.suse.com/1259891","tags":["report"]},{"url":"https://bugzilla.suse.com/1259997","tags":["report"]},{"url":"https://bugzilla.suse.com/1259998","tags":["report"]},{"url":"https://bugzilla.suse.com/1260005","tags":["report"]},{"url":"https://bugzilla.suse.com/1260009","tags":["report"]},{"url":"https://bugzilla.suse.com/1260347","tags":["report"]},{"url":"https://bugzilla.suse.com/1260464","tags":["report"]},{"url":"https://bugzilla.suse.com/1260471","tags":["report"]},{"url":"https://bugzilla.suse.com/1260481","tags":["report"]},{"url":"https://bugzilla.suse.com/1260486","tags":["report"]},{"url":"https://bugzilla.suse.com/1260500","tags":["report"]},{"url":"https://bugzilla.suse.com/1260562","tags":["report"]},{"url":"https://bugzilla.suse.com/1260730","tags":["report"]},{"url":"https://bugzilla.suse.com/1260732","tags":["report"]},{"url":"https://bugzilla.suse.com/1260735","tags":["report"]},{"url":"https://bugzilla.suse.com/1260799","tags":["report"]},{"url":"https://bugzilla.suse.com/1261496","tags":["report"]},{"url":"https://bugzilla.suse.com/1261498","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-38542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31788","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261661-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620838-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1234634","tags":["report"]},{"url":"https://bugzilla.suse.com/1249590","tags":["report"]},{"url":"https://bugzilla.suse.com/1250748","tags":["report"]},{"url":"https://bugzilla.suse.com/1251966","tags":["report"]},{"url":"https://bugzilla.suse.com/1252008","tags":["report"]},{"url":"https://bugzilla.suse.com/1252911","tags":["report"]},{"url":"https://bugzilla.suse.com/1252924","tags":["report"]},{"url":"https://bugzilla.suse.com/1253691","tags":["report"]},{"url":"https://bugzilla.suse.com/1254817","tags":["report"]},{"url":"https://bugzilla.suse.com/1254928","tags":["report"]},{"url":"https://bugzilla.suse.com/1255129","tags":["report"]},{"url":"https://bugzilla.suse.com/1255144","tags":["report"]},{"url":"https://bugzilla.suse.com/1255148","tags":["report"]},{"url":"https://bugzilla.suse.com/1255311","tags":["report"]},{"url":"https://bugzilla.suse.com/1255490","tags":["report"]},{"url":"https://bugzilla.suse.com/1255572","tags":["report"]},{"url":"https://bugzilla.suse.com/1255721","tags":["report"]},{"url":"https://bugzilla.suse.com/1255868","tags":["report"]},{"url":"https://bugzilla.suse.com/1256640","tags":["report"]},{"url":"https://bugzilla.suse.com/1256675","tags":["report"]},{"url":"https://bugzilla.suse.com/1256679","tags":["report"]},{"url":"https://bugzilla.suse.com/1256708","tags":["report"]},{"url":"https://bugzilla.suse.com/1256732","tags":["report"]},{"url":"https://bugzilla.suse.com/1256784","tags":["report"]},{"url":"https://bugzilla.suse.com/1256802","tags":["report"]},{"url":"https://bugzilla.suse.com/1256865","tags":["report"]},{"url":"https://bugzilla.suse.com/1256867","tags":["report"]},{"url":"https://bugzilla.suse.com/1257154","tags":["report"]},{"url":"https://bugzilla.suse.com/1257174","tags":["report"]},{"url":"https://bugzilla.suse.com/1257209","tags":["report"]},{"url":"https://bugzilla.suse.com/1257222","tags":["report"]},{"url":"https://bugzilla.suse.com/1257228","tags":["report"]},{"url":"https://bugzilla.suse.com/1257231","tags":["report"]},{"url":"https://bugzilla.suse.com/1257246","tags":["report"]},{"url":"https://bugzilla.suse.com/1257332","tags":["report"]},{"url":"https://bugzilla.suse.com/1257473","tags":["report"]},{"url":"https://bugzilla.suse.com/1257551","tags":["report"]},{"url":"https://bugzilla.suse.com/1257552","tags":["report"]},{"url":"https://bugzilla.suse.com/1257553","tags":["report"]},{"url":"https://bugzilla.suse.com/1257554","tags":["report"]},{"url":"https://bugzilla.suse.com/1257556","tags":["report"]},{"url":"https://bugzilla.suse.com/1257557","tags":["report"]},{"url":"https://bugzilla.suse.com/1257559","tags":["report"]},{"url":"https://bugzilla.suse.com/1257560","tags":["report"]},{"url":"https://bugzilla.suse.com/1257562","tags":["report"]},{"url":"https://bugzilla.suse.com/1257565","tags":["report"]},{"url":"https://bugzilla.suse.com/1257570","tags":["report"]},{"url":"https://bugzilla.suse.com/1257572","tags":["report"]},{"url":"https://bugzilla.suse.com/1257573","tags":["report"]},{"url":"https://bugzilla.suse.com/1257576","tags":["report"]},{"url":"https://bugzilla.suse.com/1257579","tags":["report"]},{"url":"https://bugzilla.suse.com/1257580","tags":["report"]},{"url":"https://bugzilla.suse.com/1257581","tags":["report"]},{"url":"https://bugzilla.suse.com/1257586","tags":["report"]},{"url":"https://bugzilla.suse.com/1257600","tags":["report"]},{"url":"https://bugzilla.suse.com/1257631","tags":["report"]},{"url":"https://bugzilla.suse.com/1257635","tags":["report"]},{"url":"https://bugzilla.suse.com/1257679","tags":["report"]},{"url":"https://bugzilla.suse.com/1257686","tags":["report"]},{"url":"https://bugzilla.suse.com/1257687","tags":["report"]},{"url":"https://bugzilla.suse.com/1257688","tags":["report"]},{"url":"https://bugzilla.suse.com/1257704","tags":["report"]},{"url":"https://bugzilla.suse.com/1257705","tags":["report"]},{"url":"https://bugzilla.suse.com/1257706","tags":["report"]},{"url":"https://bugzilla.suse.com/1257707","tags":["report"]},{"url":"https://bugzilla.suse.com/1257709","tags":["report"]},{"url":"https://bugzilla.suse.com/1257714","tags":["report"]},{"url":"https://bugzilla.suse.com/1257715","tags":["report"]},{"url":"https://bugzilla.suse.com/1257716","tags":["report"]},{"url":"https://bugzilla.suse.com/1257718","tags":["report"]},{"url":"https://bugzilla.suse.com/1257722","tags":["report"]},{"url":"https://bugzilla.suse.com/1257723","tags":["report"]},{"url":"https://bugzilla.suse.com/1257726","tags":["report"]},{"url":"https://bugzilla.suse.com/1257729","tags":["report"]},{"url":"https://bugzilla.suse.com/1257730","tags":["report"]},{"url":"https://bugzilla.suse.com/1257732","tags":["report"]},{"url":"https://bugzilla.suse.com/1257734","tags":["report"]},{"url":"https://bugzilla.suse.com/1257735","tags":["report"]},{"url":"https://bugzilla.suse.com/1257737","tags":["report"]},{"url":"https://bugzilla.suse.com/1257739","tags":["report"]},{"url":"https://bugzilla.suse.com/1257740","tags":["report"]},{"url":"https://bugzilla.suse.com/1257741","tags":["report"]},{"url":"https://bugzilla.suse.com/1257742","tags":["report"]},{"url":"https://bugzilla.suse.com/1257743","tags":["report"]},{"url":"https://bugzilla.suse.com/1257745","tags":["report"]},{"url":"https://bugzilla.suse.com/1257749","tags":["report"]},{"url":"https://bugzilla.suse.com/1257750","tags":["report"]},{"url":"https://bugzilla.suse.com/1257755","tags":["report"]},{"url":"https://bugzilla.suse.com/1257757","tags":["report"]},{"url":"https://bugzilla.suse.com/1257758","tags":["report"]},{"url":"https://bugzilla.suse.com/1257759","tags":["report"]},{"url":"https://bugzilla.suse.com/1257761","tags":["report"]},{"url":"https://bugzilla.suse.com/1257762","tags":["report"]},{"url":"https://bugzilla.suse.com/1257763","tags":["report"]},{"url":"https://bugzilla.suse.com/1257765","tags":["report"]},{"url":"https://bugzilla.suse.com/1257768","tags":["report"]},{"url":"https://bugzilla.suse.com/1257770","tags":["report"]},{"url":"https://bugzilla.suse.com/1257772","tags":["report"]},{"url":"https://bugzilla.suse.com/1257775","tags":["report"]},{"url":"https://bugzilla.suse.com/1257776","tags":["report"]},{"url":"https://bugzilla.suse.com/1257788","tags":["report"]},{"url":"https://bugzilla.suse.com/1257789","tags":["report"]},{"url":"https://bugzilla.suse.com/1257790","tags":["report"]},{"url":"https://bugzilla.suse.com/1257805","tags":["report"]},{"url":"https://bugzilla.suse.com/1257808","tags":["report"]},{"url":"https://bugzilla.suse.com/1257809","tags":["report"]},{"url":"https://bugzilla.suse.com/1257811","tags":["report"]},{"url":"https://bugzilla.suse.com/1257813","tags":["report"]},{"url":"https://bugzilla.suse.com/1257814","tags":["report"]},{"url":"https://bugzilla.suse.com/1257815","tags":["report"]},{"url":"https://bugzilla.suse.com/1257816","tags":["report"]},{"url":"https://bugzilla.suse.com/1257817","tags":["report"]},{"url":"https://bugzilla.suse.com/1257818","tags":["report"]},{"url":"https://bugzilla.suse.com/1257830","tags":["report"]},{"url":"https://bugzilla.suse.com/1257942","tags":["report"]},{"url":"https://bugzilla.suse.com/1257952","tags":["report"]},{"url":"https://bugzilla.suse.com/1258153","tags":["report"]},{"url":"https://bugzilla.suse.com/1258181","tags":["report"]},{"url":"https://bugzilla.suse.com/1258184","tags":["report"]},{"url":"https://bugzilla.suse.com/1258222","tags":["report"]},{"url":"https://bugzilla.suse.com/1258232","tags":["report"]},{"url":"https://bugzilla.suse.com/1258234","tags":["report"]},{"url":"https://bugzilla.suse.com/1258237","tags":["report"]},{"url":"https://bugzilla.suse.com/1258245","tags":["report"]},{"url":"https://bugzilla.suse.com/1258249","tags":["report"]},{"url":"https://bugzilla.suse.com/1258252","tags":["report"]},{"url":"https://bugzilla.suse.com/1258256","tags":["report"]},{"url":"https://bugzilla.suse.com/1258258","tags":["report"]},{"url":"https://bugzilla.suse.com/1258259","tags":["report"]},{"url":"https://bugzilla.suse.com/1258272","tags":["report"]},{"url":"https://bugzilla.suse.com/1258273","tags":["report"]},{"url":"https://bugzilla.suse.com/1258276","tags":["report"]},{"url":"https://bugzilla.suse.com/1258277","tags":["report"]},{"url":"https://bugzilla.suse.com/1258279","tags":["report"]},{"url":"https://bugzilla.suse.com/1258286","tags":["report"]},{"url":"https://bugzilla.suse.com/1258289","tags":["report"]},{"url":"https://bugzilla.suse.com/1258290","tags":["report"]},{"url":"https://bugzilla.suse.com/1258297","tags":["report"]},{"url":"https://bugzilla.suse.com/1258298","tags":["report"]},{"url":"https://bugzilla.suse.com/1258299","tags":["report"]},{"url":"https://bugzilla.suse.com/1258304","tags":["report"]},{"url":"https://bugzilla.suse.com/1258308","tags":["report"]},{"url":"https://bugzilla.suse.com/1258309","tags":["report"]},{"url":"https://bugzilla.suse.com/1258313","tags":["report"]},{"url":"https://bugzilla.suse.com/1258317","tags":["report"]},{"url":"https://bugzilla.suse.com/1258321","tags":["report"]},{"url":"https://bugzilla.suse.com/1258323","tags":["report"]},{"url":"https://bugzilla.suse.com/1258324","tags":["report"]},{"url":"https://bugzilla.suse.com/1258326","tags":["report"]},{"url":"https://bugzilla.suse.com/1258331","tags":["report"]},{"url":"https://bugzilla.suse.com/1258338","tags":["report"]},{"url":"https://bugzilla.suse.com/1258349","tags":["report"]},{"url":"https://bugzilla.suse.com/1258354","tags":["report"]},{"url":"https://bugzilla.suse.com/1258355","tags":["report"]},{"url":"https://bugzilla.suse.com/1258358","tags":["report"]},{"url":"https://bugzilla.suse.com/1258374","tags":["report"]},{"url":"https://bugzilla.suse.com/1258376","tags":["report"]},{"url":"https://bugzilla.suse.com/1258377","tags":["report"]},{"url":"https://bugzilla.suse.com/1258379","tags":["report"]},{"url":"https://bugzilla.suse.com/1258389","tags":["report"]},{"url":"https://bugzilla.suse.com/1258394","tags":["report"]},{"url":"https://bugzilla.suse.com/1258395","tags":["report"]},{"url":"https://bugzilla.suse.com/1258397","tags":["report"]},{"url":"https://bugzilla.suse.com/1258411","tags":["report"]},{"url":"https://bugzilla.suse.com/1258415","tags":["report"]},{"url":"https://bugzilla.suse.com/1258419","tags":["report"]},{"url":"https://bugzilla.suse.com/1258421","tags":["report"]},{"url":"https://bugzilla.suse.com/1258422","tags":["report"]},{"url":"https://bugzilla.suse.com/1258429","tags":["report"]},{"url":"https://bugzilla.suse.com/1258430","tags":["report"]},{"url":"https://bugzilla.suse.com/1258442","tags":["report"]},{"url":"https://bugzilla.suse.com/1258455","tags":["report"]},{"url":"https://bugzilla.suse.com/1258461","tags":["report"]},{"url":"https://bugzilla.suse.com/1258464","tags":["report"]},{"url":"https://bugzilla.suse.com/1258465","tags":["report"]},{"url":"https://bugzilla.suse.com/1258468","tags":["report"]},{"url":"https://bugzilla.suse.com/1258469","tags":["report"]},{"url":"https://bugzilla.suse.com/1258483","tags":["report"]},{"url":"https://bugzilla.suse.com/1258484","tags":["report"]},{"url":"https://bugzilla.suse.com/1258489","tags":["report"]},{"url":"https://bugzilla.suse.com/1258517","tags":["report"]},{"url":"https://bugzilla.suse.com/1258518","tags":["report"]},{"url":"https://bugzilla.suse.com/1258519","tags":["report"]},{"url":"https://bugzilla.suse.com/1258520","tags":["report"]},{"url":"https://bugzilla.suse.com/1258524","tags":["report"]},{"url":"https://bugzilla.suse.com/1258544","tags":["report"]},{"url":"https://bugzilla.suse.com/1258660","tags":["report"]},{"url":"https://bugzilla.suse.com/1258672","tags":["report"]},{"url":"https://bugzilla.suse.com/1258824","tags":["report"]},{"url":"https://bugzilla.suse.com/1259329","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23230","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620873-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620931-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621114-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1249998","tags":["report"]},{"url":"https://bugzilla.suse.com/1251186","tags":["report"]},{"url":"https://bugzilla.suse.com/1253455","tags":["report"]},{"url":"https://bugzilla.suse.com/1254306","tags":["report"]},{"url":"https://bugzilla.suse.com/1255084","tags":["report"]},{"url":"https://bugzilla.suse.com/1256645","tags":["report"]},{"url":"https://bugzilla.suse.com/1257183","tags":["report"]},{"url":"https://bugzilla.suse.com/1258293","tags":["report"]},{"url":"https://bugzilla.suse.com/1258340","tags":["report"]},{"url":"https://bugzilla.suse.com/1258832","tags":["report"]},{"url":"https://bugzilla.suse.com/1258849","tags":["report"]},{"url":"https://bugzilla.suse.com/1259461","tags":["report"]},{"url":"https://bugzilla.suse.com/1259870","tags":["report"]},{"url":"https://bugzilla.suse.com/1260497","tags":["report"]},{"url":"https://bugzilla.suse.com/1260527","tags":["report"]},{"url":"https://bugzilla.suse.com/1260544","tags":["report"]},{"url":"https://bugzilla.suse.com/1260550","tags":["report"]},{"url":"https://bugzilla.suse.com/1260580","tags":["report"]},{"url":"https://bugzilla.suse.com/1261412","tags":["report"]},{"url":"https://bugzilla.suse.com/1261507","tags":["report"]},{"url":"https://bugzilla.suse.com/1261669","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23419","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621123-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621255-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621284-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-23047","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23047","tags":["report"]},{"url":"https://git.kernel.org/linus/c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8096-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8116-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8141-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8243-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8393-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8440-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8499-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8594-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8604-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8605-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8669-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-49465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23021","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-54207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53359","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23047","title":"libceph: make calc_target() set t-\u003epaused, not just clear it","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:00:29.475Z","modified":"2026-05-11T21:58:58.513Z","updated_at":"2026-11-02T13:42:04.39372Z"}],"euvd":[{"id":"EUVD-2026-5500","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:00:29Z","modified":"2026-05-11T21:58:58Z","updated_at":"2026-11-02T19:04:45.494343Z"}],"ghsa":[{"id":"GHSA-484m-2c5w-2g38","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target()...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T18:30:41Z","modified":"2026-02-04T18:30:50Z","updated_at":"2026-11-02T15:06:02.555847Z"}],"nvd":[{"id":"CVE-2026-23047","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:16:20.227Z","modified":"2026-06-17T10:20:46.18Z","updated_at":"2026-11-02T14:12:05.149641Z"}],"osv":[{"id":"OESA-2026-1566","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.727225213Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1567","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.776858405Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1570","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:38.135892245Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2026-23047","title":"CVE-2026-23047 in linux - Patched by Root","description":"Root has patched CVE-2026-23047 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:35.139691123Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:29.631993Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-23047","title":"CVE-2026-23047 in linux - Patched by Root","description":"Root has patched CVE-2026-23047 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:17:34.575460715Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:31.773105Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23047","title":"CVE-2026-23047 in linux - Patched by Root","description":"Root has patched CVE-2026-23047 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:15:44.447029683Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-06T16:28:43.316846Z"},{"id":"BELL-CVE-2026-23047","status":"published","published":"2026-02-10T06:09:20.713022Z","modified":"2026-06-25T07:18:33.324784424Z","updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"CVE-2026-23047","title":"libceph: make calc_target() set t-\u003epaused, not just clear it","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u003epaused, not just clear it\n\nCurrently calc_target() clears t-\u003epaused if the request shouldn't be\npaused anymore, but doesn't ever set t-\u003epaused even though it's able to\ndetermine when the request should be paused.  Setting t-\u003epaused is left\nto __submit_request() which is fine for regular requests but doesn't\nwork for linger requests -- since __submit_request() doesn't operate\non linger requests, there is nowhere for lreq-\u003et.paused to be set.\nOne consequence of this is that watches don't get reestablished on\npaused -\u003e unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u003ewatch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u003ewatch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \"rbd unmap\" would inevitably\nhang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:00:29.475Z","modified":"2026-10-28T02:31:10.214739595Z","updated_at":"2026-11-02T15:44:58.749922Z"},{"id":"DEBIAN-CVE-2026-23047","description":"In the Linux kernel, the following vulnerability has been resolved:  libceph: make calc_target() set t-\u003epaused, not just clear it  Currently calc_target() clears t-\u003epaused if the request shouldn't be paused anymore, but doesn't ever set t-\u003epaused even though it's able to determine when the request should be paused.  Setting t-\u003epaused is left to __submit_request() which is fine for regular requests but doesn't work for linger requests -- since __submit_request() doesn't operate on linger requests, there is nowhere for lreq-\u003et.paused to be set. One consequence of this is that watches don't get reestablished on paused -\u003e unpaused transitions in cases where requests have been paused long enough for the (paused) unwatch request to time out and for the subsequent (re)watch request to enter the paused state.  On top of the watch not getting reestablished, rbd_reregister_watch() gets stuck with rbd_dev-\u003ewatch_mutex held:    rbd_register_watch     __rbd_register_watch       ceph_osdc_watch         linger_reg_commit_wait  It's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to happen the respective request needs to end up on need_resend_linger list and be kicked when requests are unpaused.  There is no chance for that if the request in question is never marked paused in the first place.  The fact that rbd_dev-\u003ewatch_mutex remains taken out forever then prevents the image from getting unmapped -- \"rbd unmap\" would inevitably hang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:16:20.227Z","modified":"2026-10-01T02:47:48.66866059Z","updated_at":"2026-11-02T15:45:53.516942Z"},{"id":"DLA-4475-1","title":"linux - security update","status":"published","published":"2026-02-10T00:00:00Z","modified":"2026-02-10T18:30:13.794366Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DLA-4476-1","title":"linux-6.1 - security update","status":"published","published":"2026-02-10T00:00:00Z","modified":"2026-02-10T18:30:13.970662Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DSA-6126-1","title":"linux - security update","status":"published","published":"2026-02-09T00:00:00Z","modified":"2026-03-09T02:09:24.491665Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"DSA-6127-1","title":"linux - security update","status":"published","published":"2026-02-09T00:00:00Z","modified":"2026-03-09T02:09:43.378453Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"MGASA-2026-0097","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:41.57748Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0098","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:42.526844Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2026:20416-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:49:52Z","modified":"2026-03-29T17:26:19.135696Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"SUSE-SU-2026:1573-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23259: io_uring/rw: free potentially allocated iovec on cache put failure (bsc#1259866).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: boards: fix unmet dependency on PINCTRL (git-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: cs42l43: Report insert for exotic peripherals (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: ISO: Fix defer tests being unstable (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: qca: fix ROM version reading on WCN3998 chips (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove 'scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans)' changes (bsc#1257506).\n- Revert 'drm/i915/display: Add quirk to skip retraining of dp link' (bsc#1253129).\n- Revert 'drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug' (git-fixes).\n- USB: add QUIRK_NO_BOS for video capture several devices (stable-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- cifs: Fix locking usage for tcon fields (git-fixes).\n- cifs: force interface update before a fresh session setup (git-fixes).\n- cifs: make default value of retrans as zero (git-fixes).\n- cifs: some missing initializations on replay (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- cpufreq/amd-pstate: Remove the redundant verify() function (bsc#1252803).\n- cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq (bsc#1252803).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Do not skip unrelated mode changes in DSC validation (git-fixes).\n- drm/amd/display: Fallback to boot snapshot for dispclk (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd/display: Wrap dcn32_override_min_req_memclk() in DC_FP_{START, END} (git-fixes).\n- drm/amd/pm: add missing od setting PP_OD_FEATURE_ZERO_FAN_BIT for smu v14 (git-fixes).\n- drm/amd/pm: remove invalid gpu_metrics.energy_accumulator on smu v13.0.x (stable-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd: fix dcn 2.01 check (git-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub4.1.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/vcn5: Add SMU dpm interface type (stable-fixes).\n- drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB (git-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix kernel-doc comments for some LUT properties (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: fix gpu idle power consumption issue for gfx v12 (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu: prevent immediate PASID reuse case (stable-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/exynos/vidi: Remove redundant error handling in vidi_get_modes() (stable-fixes).\n- drm/exynos: vidi: fix to avoid directly dereferencing user pointer (stable-fixes).\n- drm/exynos: vidi: use ctx-\u003elock to protect struct vidi_context member variables related to memory alloc/free\n  (stable-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state (git-fixes).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- drm/i915/dsi: Do not do DSC horizontal timing adjustments in command mode (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/imagination: Fix deadlock in soft reset sequence (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/msm: Fix dma_free_attrs() buffer size (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/ttm/tests: Fix build failure on PREEMPT_RT (stable-fixes).\n- drm/xe/oa: Allow reading after disabling OA stream (git-fixes).\n- drm/xe/reg_sr: Fix leak on xa_store failure (git-fixes).\n- drm/xe: Do not preempt fence signaling CS instructions (git-fixes).\n- drm/xe: Open-code GGTT MMIO access protection (git-fixes).\n- drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- irqchip/qcom-mpm: Add missing mailbox TX done acknowledgment (git-fixes).\n- mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations (stable-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fixes).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208). Refresh:\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- s390/debug: Pass in and enforce output buffer size for format handlers (jsc#PED-15582).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- smb: client: add proper locking around ses-\u003eiface_last_update (git-fixes).\n- smb: client: fix broken multichannel with krb5+signing (git-fixes).\n- smb: client: fix cifs_pick_channel when channels are equally loaded (git-fixes).\n- smb: client: fix in-place encryption corruption in SMB2_write() (git-fixes).\n- smb: client: fix krb5 mount with username option (git-fixes).\n- smb: client: prevent races in -\u003equery_interfaces() (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: core: new quirk to handle devices with zero configurations (stable-fixes).\n- usb: core: phy: avoid double use of 'usb3-phy' (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- vhost: fix caching attributes of MMIO regions by setting them explicitly (git-fixes).\n- vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 (git-fixes).\n- watchdog/perf: properly initialize the turbo mode timestamp and rearm counter (bsc#1256504).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n- xenbus: Use .freeze/.thaw to handle xenbus devices (git-fixes).\n","status":"published","published":"2026-04-23T15:52:40Z","modified":"2026-04-24T08:15:33.422826Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:1661-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: register hooks last when adding new chain/flowtable (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23259: io_uring/rw: free potentially allocated iovec on cache put failure (bsc#1259866).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: export bpf_link_inc_not_zero (bsc#1260735).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: cs42l43: Report insert for exotic peripherals (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: Intel: boards: fix unmet dependency on PINCTRL (git-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: ISO: Fix defer tests being unstable (git-fixes).\n- Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: qca: fix ROM version reading on WCN3998 chips (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- cifs: Fix locking usage for tcon fields (git-fixes).\n- cifs: force interface update before a fresh session setup (git-fixes).\n- cifs: make default value of retrans as zero (git-fixes).\n- cifs: some missing initializations on replay (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- cpufreq/amd-pstate: Remove the redundant verify() function (bsc#1252803).\n- cpufreq/amd-pstate: Set the initial min_freq to lowest_nonlinear_freq (bsc#1252803).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- drm: Fix use-after-free on framebuffers and property blobs when calling drm_dev_unplug (git-fixes).\n- drm/amd: fix dcn 2.01 check (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Do not skip unrelated mode changes in DSC validation (git-fixes).\n- drm/amd/display: Fallback to boot snapshot for dispclk (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd/display: Wrap dcn32_override_min_req_memclk() in DC_FP_{START, END} (git-fixes).\n- drm/amd/pm: add missing od setting PP_OD_FEATURE_ZERO_FAN_BIT for smu v14 (git-fixes).\n- drm/amd/pm: remove invalid gpu_metrics.energy_accumulator on smu v13.0.x (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB (git-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: fix gpu idle power consumption issue for gfx v12 (stable-fixes).\n- drm/amdgpu: Fix kernel-doc comments for some LUT properties (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu: prevent immediate PASID reuse case (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub4.1.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/vcn5: Add SMU dpm interface type (stable-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/exynos: vidi: fix to avoid directly dereferencing user pointer (stable-fixes).\n- drm/exynos/vidi: Remove redundant error handling in vidi_get_modes() (stable-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dp_tunnel: Fix error handling when clearing stream BW in atomic state (git-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/imagination: Fix deadlock in soft reset sequence (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm: Fix dma_free_attrs() buffer size (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/ttm/tests: Fix build failure on PREEMPT_RT (stable-fixes).\n- drm/xe: Do not preempt fence signaling CS instructions (git-fixes).\n- drm/xe: Open-code GGTT MMIO access protection (git-fixes).\n- drm/xe/oa: Allow reading after disabling OA stream (git-fixes).\n- drm/xe/reg_sr: Fix leak on xa_store failure (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: don't use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- irqchip/qcom-mpm: Add missing mailbox TX done acknowledgment (git-fixes).\n- mac80211: fix crash in ieee80211_chan_bw_change for AP_VLAN stations (stable-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: fix use-after-free in mana_hwc_destroy_channel() by reordering teardown (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fixes).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- s390/debug: Pass in and enforce output buffer size for format handlers (jsc#PED-15582.\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- smb: client: add proper locking around ses-\u003eiface_last_update (git-fixes).\n- smb: client: fix broken multichannel with krb5+signing (git-fixes).\n- smb: client: fix cifs_pick_channel when channels are equally loaded (git-fixes).\n- smb: client: fix in-place encryption corruption in SMB2_write() (git-fixes).\n- smb: client: fix krb5 mount with username option (git-fixes).\n- smb: client: prevent races in -\u003equery_interfaces() (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- USB: add QUIRK_NO_BOS for video capture several devices (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: don't power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- usb: core: new quirk to handle devices with zero configurations (stable-fixes).\n- usb: core: phy: avoid double use of 'usb3-phy' (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- vhost: fix caching attributes of MMIO regions by setting them explicitly (git-fixes).\n- vmw_vsock: bypass false-positive Wnonnull warning with gcc-16 (git-fixes).\n- watchdog/perf: properly initialize the turbo mode timestamp and rearm counter (bsc#1256504).\n- wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session (git-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n- xenbus: Use .freeze/.thaw to handle xenbus devices (git-fixes).\n","status":"published","published":"2026-04-30T12:05:10Z","modified":"2026-05-01T08:17:19.513034Z","updated_at":"2026-11-02T15:54:01.610851Z"},{"id":"SUSE-SU-2026:20838-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:48:43Z","modified":"2026-03-28T17:24:39.090411Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20873-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:52:20Z","modified":"2026-07-09T18:24:05.527764914Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20931-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:48:43Z","modified":"2026-04-02T17:24:40.319019Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:21114-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T17:04:49Z","modified":"2026-04-18T18:25:53.212585Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21123-1","title":"Security update for the Linux Kernel","description":"The SUSE Linux Enterprise Micro 6.0 and 6.1 kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths\n  (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non-security bugs were fixed:\n\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Remove \"scsi: Fix sas_user_scan() to handle wildcard and multi-channel scans\" changes (bsc#1257506).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: Reinit dev-\u003espinlock between attachments to low-level drivers (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: do not use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: dell-wmi-sysman: Do not hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- rename Hyper-v patch files to simplify further SP6-SP7 merges\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186, bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: do not power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Do not default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-13T18:28:29Z","modified":"2026-04-18T18:25:56.735736Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21255-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Micro (RT) 6.0 and 6.1 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2024-38542: RDMA/mana_ib: boundary check before installing cq callbacks (bsc#1226591).\n- CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk-\u003egroup_leader) in sys_prlimit64() paths (bsc#1253455).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent (bsc#1259865).\n- CVE-2025-71269: btrfs: do not free data reservation in fallback from inline due to -ENOSPC (bsc#1259889).\n- CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() (bsc#1257561).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: register hooks last when adding new chain/flowtable (bsc#1259188).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23317: drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (bsc#1260562).\n- CVE-2026-23319: bpf: export bpf_link_inc_not_zero (bsc#1260735).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ (bsc#1260580).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23412: netfilter: bpf: defer hook memory release until rcu readers are done (bsc#1261412).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- accel/qaic: Handle DBC deactivation if the owner went away (git-fixes).\n- ACPI: EC: clean up handlers on probe failure in acpi_ec_setup() (git-fixes).\n- ACPI: OSI: Add DMI quirk for Acer Aspire One D255 (stable-fixes).\n- ACPI: OSL: fix __iomem type on return from acpi_os_map_generic_address() (git-fixes).\n- ACPI: PM: Save NVS memory on Lenovo G70-35 (stable-fixes).\n- ACPI: processor: Fix previous acpi_processor_errata_piix4() fix (git-fixes).\n- ALSA: caiaq: fix stack out-of-bounds read in init_card (git-fixes).\n- ALSA: firewire-lib: fix uninitialized local variable (git-fixes).\n- ALSA: hda: cs35l56: Fix signedness error in cs35l56_hda_posture_put() (git-fixes).\n- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4 (stable-fixes).\n- ALSA: hda/conexant: Fix headphone jack handling on Acer Swift SF314 (stable-fixes).\n- ALSA: hda/realtek: Add headset jack quirk for Thinkpad X390 (stable-fixes).\n- ALSA: hda/realtek: add HP Laptop 14s-dr5xxx mute LED quirk (stable-fixes).\n- ALSA: pci: hda: use snd_kcontrol_chip() (stable-fixes).\n- ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain() (git-fixes).\n- ALSA: usb-audio: Check endpoint numbers at parsing Scarlett2 mixer interfaces (stable-fixes).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- ASoC: adau1372: Fix clock leak on PLL lock failure (git-fixes).\n- ASoC: adau1372: Fix unchecked clk_prepare_enable() return value (git-fixes).\n- ASoC: amd: acp-mach-common: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: acp3x-rt5682-max9836: Add missing error check for clock acquisition (git-fixes).\n- ASoC: amd: yc: Add ASUS EXPERTBOOK BM1503CDA to quirk table (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS EXPERTBOOK PM1503CDA (stable-fixes).\n- ASoC: detect empty DMI strings (git-fixes).\n- ASoC: ep93xx: Fix unchecked clk_prepare_enable() and add rollback on failure (git-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_put_bits() (stable-fixes).\n- ASoC: fsl_easrc: Fix event generation in fsl_easrc_iec958_set_reg() (stable-fixes).\n- ASoC: Intel: catpt: Fix the device initialization (git-fixes).\n- ASoC: qcom: qdsp6: Fix q6apm remove ordering during ADSP stop and start (git-fixes).\n- ASoC: soc-core: drop delayed_work_pending() check before flush (git-fixes).\n- ASoC: soc-core: flush delayed work before removing DAIs and widgets (git-fixes).\n- ASoC: SOF: ipc4-topology: Allow bytes controls without initial payload (git-fixes).\n- batman-adv: Avoid double-rtnl_lock ELP metric worker (git-fixes).\n- Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock (git-fixes).\n- Bluetooth: btusb: clamp SCO altsetting table indices (git-fixes).\n- Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt (git-fixes).\n- Bluetooth: hci_ll: Fix firmware leak on error path (git-fixes).\n- Bluetooth: hci_sync: call destroy in hci_cmd_sync_run if immediate (git-fixes).\n- Bluetooth: hci_sync: Fix hci_le_create_conn_sync (git-fixes).\n- Bluetooth: hci_sync: Remove remaining dependencies of hci_request (stable-fixes).\n- Bluetooth: HIDP: Fix possible UAF (git-fixes).\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop (git-fixes).\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb (git-fixes).\n- Bluetooth: L2CAP: Fix send LE flow credits in ACL link (git-fixes).\n- Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() (git-fixes).\n- Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user (git-fixes).\n- Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access (git-fixes).\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if received packet's SDU exceeds IMTU (git-fixes).\n- Bluetooth: LE L2CAP: Disconnect if sum of payload sizes exceed SDU (git-fixes).\n- Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete (git-fixes).\n- Bluetooth: MGMT: validate LTK enc_size on load (git-fixes).\n- Bluetooth: MGMT: validate mesh send advertising payload length (git-fixes).\n- Bluetooth: Remove 3 repeated macro definitions (stable-fixes).\n- Bluetooth: SCO: fix race conditions in sco_sock_connect() (git-fixes).\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold (git-fixes).\n- Bluetooth: SMP: derive legacy responder STK authentication from MITM state (git-fixes).\n- Bluetooth: SMP: force responder MITM requirements before building the pairing response (git-fixes).\n- Bluetooth: SMP: make SM/PER/KDU/BI-04-C happy (git-fixes).\n- bonding: do not set usable_slaves for broadcast mode (git-fixes).\n- btrfs: fix zero size inode with non-zero size after log replay (git-fixes).\n- btrfs: log new dentries when logging parent dir of a conflicting inode (git-fixes).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): check the proper length of a message (git-fixes).\n- can: gw: fix OOB heap access in cgw_csum_crc8_rel() (git-fixes).\n- can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (git-fixes).\n- can: isotp: fix tx.buf use-after-free in isotp_sendmsg() (git-fixes).\n- can: mcp251x: fix deadlock in error path of mcp251x_open (git-fixes).\n- can: ucan: Fix infinite loop from zero-length messages (git-fixes).\n- can: usb: etas_es58x: correctly anchor the urb in the read bulk callback (git-fixes).\n- comedi: me_daq: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: me4000: Fix potential overrun of firmware buffer (git-fixes).\n- comedi: ni_atmio16d: Fix invalid clean-up after failed attach (git-fixes).\n- comedi: Reinit dev-spinlock between attachments to low-level drivers (git-fixes).\n- crypto: af-alg - fix NULL pointer dereference in scatterwalk (git-fixes).\n- crypto: caam - fix DMA corruption on long hmac keys (git-fixes).\n- crypto: caam - fix overflow on long hmac keys (git-fixes).\n- dmaengine: idxd: Fix freeing the allocated ida too late (git-fixes).\n- dmaengine: idxd: Fix leaking event log memory (git-fixes).\n- dmaengine: idxd: Fix memory leak when a wq is reset (git-fixes).\n- dmaengine: idxd: Fix not releasing workqueue on .release() (git-fixes).\n- dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() (git-fixes).\n- dmaengine: idxd: Remove usage of the deprecated ida_simple_xx() API (stable-fixes).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- dmaengine: sh: rz-dmac: Protect the driver specific lists (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap init error handling (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix dma_device directions (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix residue calculation for cyclic DMA (git-fixes).\n- dmaengine: xilinx: xilinx_dma: Fix unmasked residue subtraction (git-fixes).\n- Drivers: hv: fix missing kernel-doc description for 'size' in request_arr_init() (git-fixes).\n- Drivers: hv: remove stale comment (git-fixes).\n- Drivers: hv: vmbus: Clean up sscanf format specifier in target_cpu_store() (git-fixes).\n- Drivers: hv: vmbus: Fix sysfs output format for ring buffer index (git-fixes).\n- Drivers: hv: vmbus: Fix typos in vmbus_drv.c (git-fixes).\n- drm/amd: Set num IP blocks to 0 if discovery fails (stable-fixes).\n- drm/amd/display: Add pixel_clock to amd_pp_display_configuration (stable-fixes).\n- drm/amd/display: Fix DisplayID not-found handling in parse_edid_displayid_vrr() (git-fixes).\n- drm/amdgpu: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (git-fixes).\n- drm/amdgpu: Fix use-after-free race in VM acquire (stable-fixes).\n- drm/amdgpu: keep vga memory on MacBooks with switchable graphics (stable-fixes).\n- drm/amdgpu/gmc9.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub2.3: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.1: add bounds checking for cid (stable-fixes).\n- drm/amdgpu/mmhub3.0.2: add bounds checking for cid (stable-fixes).\n- drm/ast: dp501: Fix initialization of SCU2C (git-fixes).\n- drm/bridge: ti-sn65dsi83: fix CHA_DSI_CLK_RANGE rounding (git-fixes).\n- drm/bridge: ti-sn65dsi86: Add support for DisplayPort mode with HPD (stable-fixes).\n- drm/i915/dp: Use crtc_state-\u003eenhanced_framing properly on ivb/hsw CPU eDP (git-fixes).\n- drm/i915/gmbus: fix spurious timeout on 512-byte burst reads (git-fixes).\n- drm/i915/gt: Check set_default_submission() before deferencing (git-fixes).\n- drm/ioc32: stop speculation on the drm_compat_ioctl path (git-fixes).\n- drm/msm/dsi: Document DSC related pclk_rate and hdisplay calculations (stable-fixes).\n- drm/msm/dsi: fix hdisplay calculation when programming dsi registers (git-fixes).\n- drm/msm/dsi: fix pclk rate calculation for bonded dsi (git-fixes).\n- drm/radeon: apply state adjust rules to some additional HAINAN vairants (stable-fixes).\n- drm/sched: Fix kernel-doc warning for drm_sched_job_done() (git-fixes).\n- drm/solomon: Fix page start when updating rectangle in page addressing mode (git-fixes).\n- firmware: arm_scpi: Fix device_node reference leak in probe path (git-fixes).\n- gpio: mxc: map Both Edge pad wakeup to Rising Edge (git-fixes).\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them (stable-fixes).\n- HID: apple: avoid memory leak in apple_report_fixup() (stable-fixes).\n- HID: asus: avoid memory leak in asus_report_fixup() (stable-fixes).\n- HID: magicmouse: avoid memory leak in magicmouse_report_fixup() (stable-fixes).\n- HID: mcp2221: cancel last I2C command on read error (stable-fixes).\n- hv/hv_kvp_daemon: Handle IPv4 and Ipv6 combination for keyfile format (git-fixes).\n- hv/hv_kvp_daemon: Pass NIC name to hv_get_dns_info as well (git-fixes).\n- hwmon: (adm1177) fix sysfs ABI violation and current unit conversion (git-fixes).\n- hwmon: (axi-fan-control) Make use of dev_err_probe() (stable-fixes).\n- hwmon: (axi-fan-control) Use device firmware agnostic API (stable-fixes).\n- hwmon: (it87) Check the it87_lock() return value (git-fixes).\n- hwmon: (occ) Fix division by zero in occ_show_power_1() (git-fixes).\n- hwmon: (occ) Fix missing newline in occ_show_extended() (git-fixes).\n- hwmon: (peci/cputemp) Fix crit_hyst returning delta instead of absolute temperature (git-fixes).\n- hwmon: (peci/cputemp) Fix off-by-one in cputemp_is_visible() (git-fixes).\n- hwmon: (pmbus/isl68137) Add mutex protection for AVS enable sysfs attributes (git-fixes).\n- hwmon: (pmbus/isl68137) Fix unchecked return value and use sysfs_emit() (git-fixes).\n- hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read (git-fixes).\n- hwmon: (pxe1610) Check return value of page-select write in probe (git-fixes).\n- hwmon: (tps53679) Fix device ID comparison and printing in tps53676_identify() (git-fixes).\n- hwmon: axi-fan: don't use driver_override as IRQ name (git-fixes).\n- i2c: cp2615: fix serial string NULL-deref at probe (git-fixes).\n- i2c: cp2615: replace deprecated strncpy with strscpy (stable-fixes).\n- i2c: fsi: Fix a potential leak in fsi_i2c_probe() (git-fixes).\n- i2c: pxa: defer reset on Armada 3700 when recovery is used (git-fixes).\n- idpf: nullify pointers after they are freed (git-fixes).\n- iio: accel: fix ADXL355 temperature signature value (git-fixes).\n- iio: adc: ti-adc161s626: fix buffer read on big-endian (git-fixes).\n- iio: chemical: bme680: Fix measurement wait duration calculation (git-fixes).\n- iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() (git-fixes).\n- iio: chemical: sps30_serial: fix buffer size in sps30_serial_read_meas() (git-fixes).\n- iio: dac: ad5770r: fix error return in ad5770r_read_raw() (git-fixes).\n- iio: dac: ds4424: reject -128 RAW value (git-fixes).\n- iio: frequency: adf4377: Fix duplicated soft reset mask (git-fixes).\n- iio: gyro: mpu3050-core: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050-i2c: fix pm_runtime error handling (git-fixes).\n- iio: gyro: mpu3050: Fix incorrect free_irq() variable (git-fixes).\n- iio: gyro: mpu3050: Fix irq resource leak (git-fixes).\n- iio: gyro: mpu3050: Fix out-of-sequence free_irq() (git-fixes).\n- iio: gyro: mpu3050: Move iio_device_register() to correct location (git-fixes).\n- iio: imu: bmi160: Remove potential undefined behavior in bmi160_config_pin() (git-fixes).\n- iio: imu: bno055: fix BNO055_SCAN_CH_COUNT off by one (git-fixes).\n- iio: imu: inv_icm42600: fix odr switch to the same value (git-fixes).\n- iio: imu: st_lsm6dsx: Set FIFO ODR for accelerometer and gyroscope only (git-fixes).\n- iio: light: vcnl4035: fix scan buffer on big-endian (git-fixes).\n- iio: potentiometer: mcp4131: fix double application of wiper shift (git-fixes).\n- Input: synaptics-rmi4 - fix a locking bug in an error path (git-fixes).\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex (git-fixes).\n- media: tegra-video: Use accessors for pad config 'try_*' fields (stable-fixes).\n- mfd: omap-usb-host: Convert to platform remove callback returning void (stable-fixes).\n- mfd: omap-usb-host: Fix OF populate on driver rebind (git-fixes).\n- mfd: qcom-pm8xxx: Convert to platform remove callback returning void (stable-fixes).\n- mfd: qcom-pm8xxx: Fix OF populate on driver rebind (git-fixes).\n- misc: fastrpc: possible double-free of cctx-\u003eremote_heap (git-fixes).\n- mmc: sdhci-pci-gli: fix GL9750 DMA write corruption (git-fixes).\n- mmc: sdhci: fix timing selection for 1-bit bus width (git-fixes).\n- mtd: Avoid boot crash in RedBoot partition table parser (git-fixes).\n- mtd: rawnand: brcmnand: skip DMA during panic write (git-fixes).\n- mtd: rawnand: cadence: Fix error check for dma_alloc_coherent() in cadence_nand_init() (git-fixes).\n- mtd: rawnand: pl353: make sure optimal timings are applied (git-fixes).\n- mtd: rawnand: serialize lock/unlock against other NAND operations (git-fixes).\n- mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode (stable-fixes).\n- mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode (stable-fixes).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (bsc#1251971).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix double destroy_workqueue on service rescan PCI path (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: fix use-after-free in add_adev() error path (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Handle Reset Request from MANA NIC (bsc#1245728 bsc#1251971).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (bsc#1252266).\n- net: mana: Ring doorbell at 4 CQ wraparounds (git-fixes).\n- net: mana: Support HW link state events (bsc#1253049).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- net: mana: use ethtool string helpers (git-fixes).\n- net: mana: Use mana_cleanup_port_context() for rxq cleanup (git-fixes).\n- net: nfc: nci: Fix zero-length proprietary notifications (git-fixes).\n- net: usb: aqc111: Do not perform PM inside suspend callback (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check (git-fixes).\n- net: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check (git-fixes).\n- net: usb: lan78xx: fix silent drop of packets with checksum errors (git-fixes).\n- net: usb: lan78xx: fix TX byte statistics for small packets (git-fixes).\n- net: usb: pegasus: validate USB endpoints (stable-fixes).\n- net/mana: Null service_wq on setup error to prevent double destroy (git-fix).\n- net/mlx5: Fix crash when moving to switchdev mode (git-fixes).\n- net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect (git-fixes).\n- net/x25: Fix overflow when accumulating packets (git-fixes).\n- net/x25: Fix potential double free of skb (git-fixes).\n- nfc: nci: clear NCI_DATA_EXCHANGE before calling completion callback (git-fixes).\n- nfc: nci: fix circular locking dependency in nci_close_device (git-fixes).\n- nfc: nci: free skb on nci_transceive early error paths (git-fixes).\n- NFC: nxp-nci: allow GPIOs to sleep (git-fixes).\n- NFC: pn533: bound the UART receive buffer (git-fixes).\n- nfc: rawsock: cancel tx_work before socket teardown (git-fixes).\n- nouveau/dpcd: return EBUSY for aux xfer if the device is asleep (git-fixes).\n- PCI: hv: Correct a comment (git-fixes).\n- PCI: hv: Remove unnecessary flex array in struct pci_packet (git-fixes).\n- PCI: hv: remove unnecessary module_init/exit functions (git-fixes).\n- PCI: hv: Remove unused field pci_bus in struct hv_pcibus_device (git-fixes).\n- PCI: Update BAR # and window messages (stable-fixes).\n- phy: ti: j721e-wiz: Fix device node reference leak in wiz_get_lane_phy_types() (git-fixes).\n- pinctrl: equilibrium: fix warning trace on load (git-fixes).\n- pinctrl: equilibrium: rename irq_chip function callbacks (stable-fixes).\n- pinctrl: mediatek: common: Fix probe failure for devices without EINT (git-fixes).\n- pinctrl: qcom: spmi-gpio: implement .get_direction() (git-fixes).\n- platform/olpc: olpc-xo175-ec: Fix overflow error message to print inlen (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump plaintext password data (git-fixes).\n- platform/x86: dell-wmi: Add audio/mic mute key codes (stable-fixes).\n- platform/x86: intel-hid: Add Dell 14 Plus 2-in-1 to dmi_vgbs_allow_list (stable-fixes).\n- platform/x86: intel-hid: Enable 5-button array on ThinkPad X1 Fold 16 Gen 1 (stable-fixes).\n- platform/x86: ISST: Correct locked bit width (git-fixes).\n- platform/x86: touchscreen_dmi: Add quirk for y-inverted Goodix touchscreen on SUPI S10 (stable-fixes).\n- PM: runtime: Fix a race condition related to device removal (git-fixes).\n- qmi_wwan: allow max_mtu above hard_mtu to control rx_urb_size (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (bsc#1251135).\n- RDMA/mana_ib: add additional port counters (bsc#1251135).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add device-memory support (git-fixes).\n- RDMA/mana_ib: Add EQ creation for rnic adapter (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (bsc#1251135).\n- RDMA/mana_ib: Adding and deleting GIDs (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Configure mac address in RNIC (git-fixes).\n- RDMA/mana_ib: Create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: Create and destroy rnic adapter (git-fixes).\n- RDMA/mana_ib: create and destroy RNIC cqs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create EQs for RNIC CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Enable RoCE on port 1 (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: extend query device (git-fixes).\n- RDMA/mana_ib: Fix DSCP value in modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (bsc#1251135).\n- RDMA/mana_ib: Fix missing ret value (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: Implement port parameters (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: implement uapi for creation of rnic cq (git-fixes).\n- RDMA/mana_ib: Implement uapi to create and destroy RC QP (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: introduce a helper to remove cq callbacks (git-fixes).\n- RDMA/mana_ib: Introduce helpers to create and destroy mana queues (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_get_netdev helper function (git-fixes).\n- RDMA/mana_ib: Introduce mana_ib_install_cq_cb helper function (git-fixes).\n- RDMA/mana_ib: Introduce mdev_to_gc helper function (git-fixes).\n- RDMA/mana_ib: Modify QP state (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Process QP error events in mana_ib (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: remove useless return values from dbg prints (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: Set correct device into ib (git-fixes).\n- RDMA/mana_ib: set node_guid (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (bsc#1251135).\n- RDMA/mana_ib: Take CQ type from the device type (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use num_comp_vectors of ib_device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (bsc#1251135).\n- RDMA/mana_ib: Use struct mana_ib_queue for CQs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for RAW QPs (git-fixes).\n- RDMA/mana_ib: Use struct mana_ib_queue for WQs (git-fixes).\n- regmap: Synchronize cache for the page selector (git-fixes).\n- regulator: pca9450: Correct interrupt type (git-fixes).\n- regulator: pca9450: Make IRQ optional (stable-fixes).\n- remoteproc: sysmon: Correct subsys_name_len type in QMI request (git-fixes).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: mpi3mr: Event processing debug improvement (bsc#1251186 bsc#1258832).\n- scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT (git-fixes).\n- scsi: storvsc: Remove redundant ternary operators (git-fixes).\n- selftests/powerpc: make sub-folders buildable on their own (bsc#1261669 ltc#212590).\n- selftests/powerpc: Re-order *FLAGS to follow lib.mk (bsc#1261669 ltc#212590).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- serial: 8250_pci: add support for the AX99100 (stable-fixes).\n- serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY (git-fixes).\n- serial: 8250: Fix TX deadlock when using DMA (git-fixes).\n- serial: uartlite: fix PM runtime usage count underflow on probe (git-fixes).\n- soc: aspeed: socinfo: Mask table entries for accurate SoC ID matching (git-fixes).\n- soc: fsl: qbman: fix race condition in qman_destroy_fq (git-fixes).\n- spi: fix statistics allocation (git-fixes).\n- spi: fix use-after-free on controller registration failure (git-fixes).\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) (git-fixes).\n- staging: rtl8723bs: properly validate the data in rtw_get_ie_ex() (stable-fixes).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- thunderbolt: Fix property read in nhi_wake_supported() (git-fixes).\n- tools: hv: Enable debug logs for hv_kvp_daemon (git-fixes).\n- tools: hv: lsvmbus: change shebang to use python3 (git-fixes).\n- tools/hv: add a .gitignore file (git-fixes).\n- tools/hv: reduce resouce usage in hv_get_dns_info helper (git-fixes).\n- tools/hv: reduce resource usage in hv_kvp_daemon (git-fixes).\n- usb: cdc-acm: Restore CAP_BRK functionnality to CH343 (git-fixes).\n- usb: cdns3: call cdns_power_is_lost() only once in cdns_resume() (stable-fixes).\n- usb: cdns3: fix role switching during resume (git-fixes).\n- usb: cdns3: gadget: fix NULL pointer dereference in ep_queue (git-fixes).\n- usb: cdns3: gadget: fix state inconsistency on gadget init failure (git-fixes).\n- usb: cdns3: remove redundant if branch (stable-fixes).\n- usb: class: cdc-wdm: fix reordering issue in read code path (git-fixes).\n- usb: core: don't power off roothub PHYs if phy_set_mode() fails (git-fixes).\n- USB: core: Limit the length of unkillable synchronous timeouts (git-fixes).\n- USB: dummy-hcd: Fix interrupt synchronization error (git-fixes).\n- USB: dummy-hcd: Fix locking/synchronization error (git-fixes).\n- usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() (git-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -H (stable-fixes).\n- usb: ehci-brcm: fix sleep during atomic (git-fixes).\n- USB: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed (stable-fixes).\n- usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks() (git-fixes).\n- usb: gadget: f_rndis: Protect RNDIS options with mutex (git-fixes).\n- usb: gadget: f_subset: Fix unbalanced refcnt in geth_free (git-fixes).\n- usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop (git-fixes).\n- usb: gadget: uvc: fix NULL pointer dereference during unbind race (git-fixes).\n- usb: image: mdc800: kill download URB on timeout (stable-fixes).\n- usb: mdc800: handle signal and read racing (stable-fixes).\n- usb: misc: uss720: properly clean up reference in uss720_probe() (stable-fixes).\n- usb: renesas_usbhs: fix use-after-free in ISR during device removal (git-fixes).\n- usb: roles: get usb role switch from parent only for usb-b-connector (git-fixes).\n- USB: serial: f81232: fix incomplete serial port generation (stable-fixes).\n- usb: ulpi: fix double free in ulpi_register_interface() error path (git-fixes).\n- USB: usbcore: Introduce usb_bulk_msg_killable() (git-fixes).\n- usb: usbtmc: Flush anchored URBs in usbtmc_release (git-fixes).\n- USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts (git-fixes).\n- usb: xhci: Fix memory leak in xhci_disable_slot() (git-fixes).\n- usb: xhci: Prevent interrupt storm on host controller error (HCE) (stable-fixes).\n- usb: yurex: fix race in probe (stable-fixes).\n- usb/core/quirks: Add Huawei ME906S-device to wakeup quirk (stable-fixes).\n- wifi: cfg80211: cancel pmsr_free_wk in cfg80211_pmsr_wdev_down (git-fixes).\n- wifi: cw1200: Fix locking in error paths (git-fixes).\n- wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler() (git-fixes).\n- wifi: mac80211: fix NULL deref in mesh_matches_local() (git-fixes).\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable (git-fixes).\n- wifi: mac80211: set default WMM parameters on all links (stable-fixes).\n- wifi: mt76: Fix possible oob access in mt76_connac2_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7925: Fix possible oob access in mt7925_mac_write_txwi_80211() (git-fixes).\n- wifi: mt76: mt7996: Fix possible oob access in mt7996_mac_write_txwi_80211() (git-fixes).\n- wifi: rsi: Don't default to -EOPNOTSUPP in rsi_mac80211_config (git-fixes).\n- wifi: wilc1000: fix u8 overflow in SSID scan buffer size calculation (git-fixes).\n- wifi: wlcore: Fix a locking bug (git-fixes).\n- wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom (git-fixes).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n- xen/privcmd: unregister xenstore notifier on module exit (git-fixes).\n","status":"published","published":"2026-04-17T15:00:24Z","modified":"2026-04-24T18:25:08.602484Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21284-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:43:53Z","modified":"2026-04-28T18:24:35.206923Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"UBUNTU-CVE-2026-23047","description":"In the Linux kernel, the following vulnerability has been resolved: libceph: make calc_target() set t-\u003epaused, not just clear it Currently calc_target() clears t-\u003epaused if the request shouldn't be paused anymore, but doesn't ever set t-\u003epaused even though it's able to determine when the request should be paused.  Setting t-\u003epaused is left to __submit_request() which is fine for regular requests but doesn't work for linger requests -- since __submit_request() doesn't operate on linger requests, there is nowhere for lreq-\u003et.paused to be set. One consequence of this is that watches don't get reestablished on paused -\u003e unpaused transitions in cases where requests have been paused long enough for the (paused) unwatch request to time out and for the subsequent (re)watch request to enter the paused state.  On top of the watch not getting reestablished, rbd_reregister_watch() gets stuck with rbd_dev-\u003ewatch_mutex held:   rbd_register_watch     __rbd_register_watch       ceph_osdc_watch         linger_reg_commit_wait It's waiting for lreq-\u003ereg_commit_wait to be completed, but for that to happen the respective request needs to end up on need_resend_linger list and be kicked when requests are unpaused.  There is no chance for that if the request in question is never marked paused in the first place. The fact that rbd_dev-\u003ewatch_mutex remains taken out forever then prevents the image from getting unmapped -- \"rbd unmap\" would inevitably hang in D state on an attempt to grab the mutex.","status":"published","published":"2026-02-04T16:16:00Z","modified":"2026-11-11T09:39:27.210982861Z","updated_at":"2026-11-11T10:01:20.456291Z"},{"id":"USN-8096-1","title":"linux, linux-aws, linux-gcp, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-intel-iotg, linux-kvm, linux-lowlatency, linux-nvidia, linux-nvidia-tegra, linux-nvidia-tegra-5.15, linux-oracle, linux-xilinx-zynqmp vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-16T14:37:39Z","modified":"2026-11-04T20:04:43.478113664Z","updated_at":"2026-11-04T21:43:05.815601Z"},{"id":"USN-8096-2","title":"linux-fips, linux-aws-fips, linux-gcp-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-16T23:26:32Z","modified":"2026-11-04T20:01:32.668181992Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-3","title":"linux-aws-5.15, linux-gcp-5.15, linux-gke, linux-hwe-5.15, linux-intel-iotg-5.15, linux-lowlatency-hwe-5.15, linux-oracle-5.15 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-17T18:58:02Z","modified":"2026-11-04T20:02:21.623692755Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-4","title":"linux-realtime vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-17T19:09:30Z","modified":"2026-11-04T20:00:55.121160644Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-5","title":"linux-nvidia-tegra-igx vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-23T13:50:16Z","modified":"2026-11-04T20:00:59.234569299Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8116-1","title":"linux-intel-iot-realtime vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-23T13:40:40Z","modified":"2026-11-04T20:01:42.2116858Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8141-1","title":"linux-raspi vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2024-36903, CVE-2024-36927,\nCVE-2024-37354, CVE-2024-41014, CVE-2024-46830, CVE-2024-47666,\nCVE-2024-49968, CVE-2024-53114, CVE-2024-56538, CVE-2024-58011,\nCVE-2025-21780, CVE-2025-21861, CVE-2025-22022, CVE-2025-22058,\nCVE-2025-22111, CVE-2025-22121, CVE-2025-23143, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38236, CVE-2025-38248, CVE-2025-38556,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40040, CVE-2025-40042, CVE-2025-40043,\nCVE-2025-40044, CVE-2025-40048, CVE-2025-40049, CVE-2025-40053,\nCVE-2025-40055, CVE-2025-40060, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40078, CVE-2025-40081, CVE-2025-40083, CVE-2025-40085,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40092, CVE-2025-40094,\nCVE-2025-40105, CVE-2025-40106, CVE-2025-40109, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40115, CVE-2025-40116,\nCVE-2025-40118, CVE-2025-40120, CVE-2025-40121, CVE-2025-40124,\nCVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40134,\nCVE-2025-40140, CVE-2025-40153, CVE-2025-40154, CVE-2025-40167,\nCVE-2025-40171, CVE-2025-40173, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40194,\nCVE-2025-40200, CVE-2025-40204, CVE-2025-40205, CVE-2025-40211,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68185, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68194, CVE-2025-68200, CVE-2025-68204,\nCVE-2025-68217, CVE-2025-68220, CVE-2025-68227, CVE-2025-68229,\nCVE-2025-68238, CVE-2025-68241, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-71064,\nCVE-2025-71066, CVE-2025-71068, CVE-2025-71069, CVE-2025-71075,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71091, CVE-2025-71093,\nCVE-2025-71094, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71102, CVE-2025-71104, CVE-2025-71105, CVE-2025-71108,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71116, CVE-2025-71118, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71125, CVE-2025-71127, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71136, CVE-2025-71137, CVE-2025-71147,\nCVE-2025-71154, CVE-2025-71180, CVE-2025-71182, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23047)\n","status":"published","published":"2026-04-01T15:16:17Z","modified":"2026-11-04T20:01:19.439094326Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8163-1","title":"linux-azure-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53041, CVE-2024-36903,\nCVE-2024-36927, CVE-2024-37354, CVE-2024-41014, CVE-2024-46830,\nCVE-2024-47666, CVE-2024-49968, CVE-2024-53114, CVE-2024-56538,\nCVE-2024-58011, CVE-2025-21780, CVE-2025-21861, CVE-2025-22022,\nCVE-2025-22058, CVE-2025-22111, CVE-2025-22121, CVE-2025-23143,\nCVE-2025-37849, CVE-2025-38022, CVE-2025-38129, CVE-2025-38236,\nCVE-2025-38248, CVE-2025-38556, CVE-2025-38584, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40167, CVE-2025-40171, CVE-2025-40173,\nCVE-2025-40178, CVE-2025-40179, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40194, CVE-2025-40200, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40211, CVE-2025-40215, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40223, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40240, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40304,\nCVE-2025-40306, CVE-2025-40308, CVE-2025-40309, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40319, CVE-2025-40321, CVE-2025-40322, CVE-2025-40324,\nCVE-2025-40331, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40349, CVE-2025-40351, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68176, CVE-2025-68177,\nCVE-2025-68185, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68200, CVE-2025-68204, CVE-2025-68217, CVE-2025-68220,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68249, CVE-2025-68254,\nCVE-2025-68255, CVE-2025-68257, CVE-2025-68258, CVE-2025-68261,\nCVE-2025-68264, CVE-2025-68266, CVE-2025-68282, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68308, CVE-2025-68312,\nCVE-2025-68321, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68366, CVE-2025-68367, CVE-2025-68372,\nCVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68734, CVE-2025-68740, CVE-2025-68746,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68767, CVE-2025-68769, CVE-2025-68771,\nCVE-2025-68774, CVE-2025-68776, CVE-2025-68777, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68808, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-71064, CVE-2025-71066, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71075, CVE-2025-71077, CVE-2025-71078,\nCVE-2025-71079, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71108, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71125, CVE-2025-71127,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71147, CVE-2025-71154, CVE-2025-71180,\nCVE-2025-71182, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978,\nCVE-2026-22980, CVE-2026-22982, CVE-2026-22984, CVE-2026-22990,\nCVE-2026-22991, CVE-2026-22992, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23047, CVE-2026-23060, CVE-2026-23074,\nCVE-2026-23111, CVE-2026-23202, CVE-2026-23207)\n","status":"published","published":"2026-04-09T23:26:12Z","modified":"2026-11-04T20:01:30.971787913Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8163-2","title":"linux-azure vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53041, CVE-2024-36903,\nCVE-2024-36927, CVE-2024-37354, CVE-2024-41014, CVE-2024-46830,\nCVE-2024-47666, CVE-2024-49968, CVE-2024-53114, CVE-2024-56538,\nCVE-2024-58011, CVE-2025-21780, CVE-2025-21861, CVE-2025-22022,\nCVE-2025-22058, CVE-2025-22111, CVE-2025-22121, CVE-2025-23143,\nCVE-2025-37849, CVE-2025-38022, CVE-2025-38129, CVE-2025-38236,\nCVE-2025-38248, CVE-2025-38556, CVE-2025-38584, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40167, CVE-2025-40171, CVE-2025-40173,\nCVE-2025-40178, CVE-2025-40179, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40194, CVE-2025-40200, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40211, CVE-2025-40215, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40223, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40240, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40304,\nCVE-2025-40306, CVE-2025-40308, CVE-2025-40309, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40319, CVE-2025-40321, CVE-2025-40322, CVE-2025-40324,\nCVE-2025-40331, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40349, CVE-2025-40351, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68176, CVE-2025-68177,\nCVE-2025-68185, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68200, CVE-2025-68204, CVE-2025-68217, CVE-2025-68220,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68249, CVE-2025-68254,\nCVE-2025-68255, CVE-2025-68257, CVE-2025-68258, CVE-2025-68261,\nCVE-2025-68264, CVE-2025-68266, CVE-2025-68282, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68308, CVE-2025-68312,\nCVE-2025-68321, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68366, CVE-2025-68367, CVE-2025-68372,\nCVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68734, CVE-2025-68740, CVE-2025-68746,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68767, CVE-2025-68769, CVE-2025-68771,\nCVE-2025-68774, CVE-2025-68776, CVE-2025-68777, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68808, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-71064, CVE-2025-71066, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71075, CVE-2025-71077, CVE-2025-71078,\nCVE-2025-71079, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71108, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71125, CVE-2025-71127,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71147, CVE-2025-71154, CVE-2025-71180,\nCVE-2025-71182, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978,\nCVE-2026-22980, CVE-2026-22982, CVE-2026-22984, CVE-2026-22990,\nCVE-2026-22991, CVE-2026-22992, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23047, CVE-2026-23060, CVE-2026-23074,\nCVE-2026-23111, CVE-2026-23202, CVE-2026-23207)\n","status":"published","published":"2026-04-13T23:59:31Z","modified":"2026-11-04T20:01:02.954045618Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8243-1","title":"linux-azure-5.15 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - NFC subsystem;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - IRQ subsystem;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53421, CVE-2023-53520,\nCVE-2023-53662, CVE-2023-54207, CVE-2024-36903, CVE-2024-36927,\nCVE-2024-37354, CVE-2024-41014, CVE-2024-46830, CVE-2024-47666,\nCVE-2024-49968, CVE-2024-53114, CVE-2024-56538, CVE-2024-58011,\nCVE-2025-21780, CVE-2025-21861, CVE-2025-22022, CVE-2025-22058,\nCVE-2025-22111, CVE-2025-22121, CVE-2025-23143, CVE-2025-37849,\nCVE-2025-38022, CVE-2025-38057, CVE-2025-38125, CVE-2025-38129,\nCVE-2025-38232, CVE-2025-38236, CVE-2025-38248, CVE-2025-38408,\nCVE-2025-38556, CVE-2025-38584, CVE-2025-38591, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40149,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40164, CVE-2025-40167,\nCVE-2025-40171, CVE-2025-40173, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40194,\nCVE-2025-40200, CVE-2025-40204, CVE-2025-40205, CVE-2025-40211,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68185, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68194, CVE-2025-68200, CVE-2025-68204,\nCVE-2025-68211, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68249, CVE-2025-68254, CVE-2025-68255,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68261, CVE-2025-68264,\nCVE-2025-68266, CVE-2025-68282, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68301, CVE-2025-68302,\nCVE-2025-68303, CVE-2025-68308, CVE-2025-68312, CVE-2025-68321,\nCVE-2025-68325, CVE-2025-68327, CVE-2025-68328, CVE-2025-68330,\nCVE-2025-68331, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68339, CVE-2025-68340, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68372, CVE-2025-68724, CVE-2025-68725, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71162, CVE-2025-71163,\nCVE-2025-71180, CVE-2025-71182, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71190, CVE-2025-71191, CVE-2025-71194,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71199, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23011, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23056,\nCVE-2026-23058, CVE-2026-23060, CVE-2026-23061, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23071, CVE-2026-23073, CVE-2026-23074,\nCVE-2026-23075, CVE-2026-23076, CVE-2026-23078, CVE-2026-23080,\nCVE-2026-23083, CVE-2026-23084, CVE-2026-23085, CVE-2026-23087,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23101, CVE-2026-23103, CVE-2026-23105,\nCVE-2026-23108, CVE-2026-23111, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23146, CVE-2026-23150, CVE-2026-23164,\nCVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-05-07T08:44:20Z","modified":"2026-11-04T20:02:34.955235626Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8278-1","title":"linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-raspi, linux-raspi-realtime, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-19T22:33:02Z","modified":"2026-11-05T19:04:28.160890429Z","updated_at":"2026-11-05T19:27:14.534654Z"},{"id":"USN-8278-2","title":"linux-azure vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-26T19:00:47Z","modified":"2026-11-05T19:01:25.946958298Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"id":"USN-8289-1","title":"linux-nvidia, linux-nvidia-lowlatency vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-20T23:06:37Z","modified":"2026-11-05T19:03:53.913181128Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8289-2","title":"linux-nvidia-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-25T17:48:27Z","modified":"2026-11-05T19:03:51.918692229Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8296-1","title":"linux-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-22T13:39:49Z","modified":"2026-11-04T20:02:47.669069853Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8296-2","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  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-25T16:46:50Z","modified":"2026-11-04T20:02:40.473452713Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8393-1","title":"linux-azure-fips vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43494, CVE-2026-46028)\n","status":"published","published":"2026-06-04T22:10:25Z","modified":"2026-11-07T01:45:07.221179684Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8440-1","title":"linux-azure-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PHY drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\n  - Shadow Call Stack mechanism;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - Packet sockets;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-57795, CVE-2024-58096, CVE-2024-58097,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-37926, CVE-2025-38022,\nCVE-2025-38201, CVE-2025-38234, CVE-2025-38591, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-40164, CVE-2025-40325,\nCVE-2025-68206, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68291, CVE-2025-68325, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68351,\nCVE-2025-68354, CVE-2025-68358, CVE-2025-68362, CVE-2025-68363,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68725, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68749, CVE-2025-68753,\nCVE-2025-68755, CVE-2025-68756, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68763, CVE-2025-68764, CVE-2025-68765,\nCVE-2025-68766, CVE-2025-68767, CVE-2025-68769, CVE-2025-68770,\nCVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774,\nCVE-2025-68775, CVE-2025-68776, CVE-2025-68777, CVE-2025-68778,\nCVE-2025-68780, CVE-2025-68782, CVE-2025-68783, CVE-2025-68785,\nCVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2025-71160,\nCVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182,\nCVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71220, CVE-2025-71222, CVE-2025-71224,\nCVE-2025-71225, CVE-2025-71268, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998,\nCVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23010, CVE-2026-23011,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23035, CVE-2026-23037, CVE-2026-23038,\nCVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23068, CVE-2026-23069,\nCVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23105, CVE-2026-23107, CVE-2026-23108,\nCVE-2026-23110, CVE-2026-23112, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23209,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23231, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43362, CVE-2026-43494, CVE-2026-46028, CVE-2026-46323)\n","status":"published","published":"2026-06-16T22:30:05Z","modified":"2026-11-07T01:45:16.546246471Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8499-1","title":"linux-xilinx vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Intel NPU Driver;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Counter interface drivers;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - MediaTek SoC drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - ChipIdea USB driver;\n  - DesignWare USB3 driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - HFS+ file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel kexec() syscall;\n  - RCU subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - Memory management;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC 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  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SOF drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40005, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-68351, CVE-2025-68358,\nCVE-2025-68365, CVE-2025-68725, CVE-2025-68749, CVE-2025-68803,\nCVE-2025-68823, CVE-2025-71160, CVE-2025-71162, CVE-2025-71163,\nCVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184,\nCVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71189,\nCVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193,\nCVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197,\nCVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71220,\nCVE-2025-71222, CVE-2025-71224, CVE-2025-71225, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71268,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71291, CVE-2025-71292, CVE-2025-71294, CVE-2025-71295,\nCVE-2025-71297, CVE-2025-71304, CVE-2025-71305, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23100,\nCVE-2026-23101, CVE-2026-23102, CVE-2026-23103, CVE-2026-23105,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23110, CVE-2026-23113,\nCVE-2026-23116, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23123, CVE-2026-23124, CVE-2026-23125, CVE-2026-23126,\nCVE-2026-23128, CVE-2026-23129, CVE-2026-23131, CVE-2026-23133,\nCVE-2026-23135, CVE-2026-23136, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23144, CVE-2026-23145,\nCVE-2026-23146, CVE-2026-23148, CVE-2026-23150, CVE-2026-23151,\nCVE-2026-23156, CVE-2026-23159, CVE-2026-23160, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23166, CVE-2026-23167, CVE-2026-23168,\nCVE-2026-23169, CVE-2026-23170, CVE-2026-23172, CVE-2026-23173,\nCVE-2026-23176, CVE-2026-23178, CVE-2026-23179, CVE-2026-23180,\nCVE-2026-23182, CVE-2026-23187, CVE-2026-23190, CVE-2026-23191,\nCVE-2026-23193, CVE-2026-23198, CVE-2026-23200, CVE-2026-23202,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23212,\nCVE-2026-23213, CVE-2026-23214, CVE-2026-23215, CVE-2026-23216,\nCVE-2026-23220, CVE-2026-23221, CVE-2026-23222, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23249,\nCVE-2026-23254, CVE-2026-23256, CVE-2026-23257, CVE-2026-23258,\nCVE-2026-23260, CVE-2026-23261, CVE-2026-23262, CVE-2026-23264,\nCVE-2026-23266, CVE-2026-23267, CVE-2026-23272, CVE-2026-23274,\nCVE-2026-23278, CVE-2026-23351, CVE-2026-23392, CVE-2026-23394,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31411, CVE-2026-31418, CVE-2026-31419, CVE-2026-31436,\nCVE-2026-31448, CVE-2026-31478, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31607, CVE-2026-31637, CVE-2026-31649, CVE-2026-31657,\nCVE-2026-31659, CVE-2026-31668, CVE-2026-31669, CVE-2026-31676,\nCVE-2026-31682, CVE-2026-31685, CVE-2026-31687, CVE-2026-31693,\nCVE-2026-43011, CVE-2026-43033, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43071, CVE-2026-43077, CVE-2026-43078, CVE-2026-43114,\nCVE-2026-43117, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43163, CVE-2026-43167,\nCVE-2026-43168, CVE-2026-43169, CVE-2026-43170, CVE-2026-43171,\nCVE-2026-43173, CVE-2026-43175, CVE-2026-43180, CVE-2026-43182,\nCVE-2026-43183, CVE-2026-43184, CVE-2026-43186, CVE-2026-43187,\nCVE-2026-43189, CVE-2026-43190, CVE-2026-43194, CVE-2026-43196,\nCVE-2026-43199, CVE-2026-43200, CVE-2026-43201, CVE-2026-43202,\nCVE-2026-43203, CVE-2026-43205, CVE-2026-43206, CVE-2026-43207,\nCVE-2026-43209, CVE-2026-43211, CVE-2026-43212, CVE-2026-43214,\nCVE-2026-43215, CVE-2026-43218, CVE-2026-43221, CVE-2026-43222,\nCVE-2026-43223, CVE-2026-43225, CVE-2026-43226, CVE-2026-43227,\nCVE-2026-43230, CVE-2026-43231, CVE-2026-43232, CVE-2026-43233,\nCVE-2026-43236, CVE-2026-43238, CVE-2026-43239, CVE-2026-43241,\nCVE-2026-43242, CVE-2026-43244, CVE-2026-43246, CVE-2026-43248,\nCVE-2026-43249, CVE-2026-43250, CVE-2026-43251, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43283, CVE-2026-43287, CVE-2026-43288,\nCVE-2026-43289, CVE-2026-43291, CVE-2026-43295, CVE-2026-43296,\nCVE-2026-43297, CVE-2026-43300, CVE-2026-43302, CVE-2026-43304,\nCVE-2026-43312, CVE-2026-43313, CVE-2026-43314, CVE-2026-43315,\nCVE-2026-43316, CVE-2026-43317, CVE-2026-43318, CVE-2026-43319,\nCVE-2026-43320, CVE-2026-43341, CVE-2026-43378, CVE-2026-43383,\nCVE-2026-43384, CVE-2026-43406, CVE-2026-43407, CVE-2026-43414,\nCVE-2026-43493, CVE-2026-43494, CVE-2026-43501, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45859, CVE-2026-45860,\nCVE-2026-45861, CVE-2026-45862, CVE-2026-45864, CVE-2026-45865,\nCVE-2026-45866, CVE-2026-45867, CVE-2026-45868, CVE-2026-45869,\nCVE-2026-45870, CVE-2026-45871, CVE-2026-45872, CVE-2026-45873,\nCVE-2026-45875, CVE-2026-45877, CVE-2026-45878, CVE-2026-45879,\nCVE-2026-45880, CVE-2026-45881, CVE-2026-45882, CVE-2026-45883,\nCVE-2026-45884, CVE-2026-45885, CVE-2026-45886, CVE-2026-45890,\nCVE-2026-45891, CVE-2026-45893, CVE-2026-45895, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45928, CVE-2026-45935, CVE-2026-45936, CVE-2026-45938,\nCVE-2026-45941, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45957, CVE-2026-45960, CVE-2026-45962,\nCVE-2026-45964, CVE-2026-45965, CVE-2026-45968, CVE-2026-45969,\nCVE-2026-45970, CVE-2026-45973, CVE-2026-45974, CVE-2026-45976,\nCVE-2026-45978, CVE-2026-45981, CVE-2026-45982, CVE-2026-45983,\nCVE-2026-45984, CVE-2026-45988, CVE-2026-46028, CVE-2026-46043,\nCVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46185,\nCVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46261, CVE-2026-46265, CVE-2026-46266, CVE-2026-46267,\nCVE-2026-46270, CVE-2026-46289, CVE-2026-46323, CVE-2026-46328)\n","status":"published","published":"2026-07-02T15:56:51Z","modified":"2026-11-07T01:45:08.338519599Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8570-1","title":"linux-gcp-6.17, linux-realtime-6.17 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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-46290, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-20T15:55:42Z","modified":"2026-11-06T13:48:59.725228621Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8570-2","title":"linux-oracle-6.17 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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-46290, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-28T07:19:37Z","modified":"2026-11-06T13:48:59.380704637Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8594-1","title":"linux-oem-6.17 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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-43318, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-23T07:42:15Z","modified":"2026-11-06T13:48:41.115427249Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8604-1","title":"linux-azure-6.17 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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - USB over IP driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Kernel thread helper (kthread);\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986,\nCVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000,\nCVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008,\nCVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012,\nCVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017,\nCVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036,\nCVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044,\nCVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049,\nCVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066,\nCVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070,\nCVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23079,\nCVE-2026-23080, CVE-2026-23081, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23092, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23100, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23104, CVE-2026-23105,\nCVE-2026-23106, CVE-2026-23107, CVE-2026-23108, CVE-2026-23109,\nCVE-2026-23110, CVE-2026-23113, CVE-2026-23114, CVE-2026-23115,\nCVE-2026-23116, CVE-2026-23118, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23122, CVE-2026-23123, CVE-2026-23124,\nCVE-2026-23125, CVE-2026-23126, CVE-2026-23128, CVE-2026-23129,\nCVE-2026-23130, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23137, CVE-2026-23138, CVE-2026-23139,\nCVE-2026-23140, CVE-2026-23141, CVE-2026-23142, CVE-2026-23143,\nCVE-2026-23144, CVE-2026-23145, CVE-2026-23146, CVE-2026-23147,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23152,\nCVE-2026-23154, CVE-2026-23156, CVE-2026-23157, CVE-2026-23158,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23161, CVE-2026-23162,\nCVE-2026-23163, CVE-2026-23164, CVE-2026-23165, CVE-2026-23166,\nCVE-2026-23167, CVE-2026-23168, CVE-2026-23169, CVE-2026-23170,\nCVE-2026-23171, CVE-2026-23172, CVE-2026-23173, CVE-2026-23212,\nCVE-2026-23272, CVE-2026-23278, CVE-2026-23392, CVE-2026-23427,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31418, CVE-2026-31436, CVE-2026-31448, CVE-2026-31478,\nCVE-2026-31607, CVE-2026-31635, CVE-2026-31637, CVE-2026-31649,\nCVE-2026-31657, CVE-2026-31659, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31682, CVE-2026-31685, CVE-2026-31718, CVE-2026-43011,\nCVE-2026-43037, CVE-2026-43038, CVE-2026-43071, CVE-2026-43083,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43125, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43197, CVE-2026-43304, CVE-2026-43341,\nCVE-2026-43376, CVE-2026-43378, CVE-2026-43383, CVE-2026-43384,\nCVE-2026-43402, CVE-2026-43406, CVE-2026-43407, CVE-2026-43414,\nCVE-2026-43493, CVE-2026-43501, CVE-2026-45898, CVE-2026-45988,\nCVE-2026-46039, CVE-2026-46043, CVE-2026-46084, CVE-2026-46115,\nCVE-2026-46119, CVE-2026-46135, CVE-2026-46185, CVE-2026-46195,\nCVE-2026-46243, CVE-2026-46244, CVE-2026-46266, CVE-2026-46289,\nCVE-2026-46290, CVE-2026-46316, CVE-2026-46317, CVE-2026-46325,\nCVE-2026-53277, CVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:07:12Z","modified":"2026-11-07T01:45:21.579104128Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8605-1","title":"linux-azure-fde-6.17 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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - USB over IP driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Kernel thread helper (kthread);\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986,\nCVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000,\nCVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008,\nCVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012,\nCVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017,\nCVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036,\nCVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044,\nCVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049,\nCVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066,\nCVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070,\nCVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-23272,\nCVE-2026-23278, CVE-2026-23392, CVE-2026-23427, CVE-2026-23428,\nCVE-2026-23450, CVE-2026-23455, CVE-2026-31402, CVE-2026-31418,\nCVE-2026-31436, CVE-2026-31448, CVE-2026-31478, CVE-2026-31607,\nCVE-2026-31635, CVE-2026-31637, CVE-2026-31649, CVE-2026-31657,\nCVE-2026-31659, CVE-2026-31668, CVE-2026-31669, CVE-2026-31682,\nCVE-2026-31685, CVE-2026-31718, CVE-2026-43011, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43071, CVE-2026-43083, CVE-2026-43114,\nCVE-2026-43117, CVE-2026-43125, CVE-2026-43185, CVE-2026-43186,\nCVE-2026-43197, CVE-2026-43304, CVE-2026-43341, CVE-2026-43376,\nCVE-2026-43378, CVE-2026-43383, CVE-2026-43384, CVE-2026-43402,\nCVE-2026-43406, CVE-2026-43407, CVE-2026-43414, CVE-2026-43493,\nCVE-2026-43501, CVE-2026-45898, CVE-2026-45988, CVE-2026-46039,\nCVE-2026-46043, CVE-2026-46084, CVE-2026-46115, CVE-2026-46119,\nCVE-2026-46135, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243,\nCVE-2026-46244, CVE-2026-46266, CVE-2026-46289, CVE-2026-46290,\nCVE-2026-46316, CVE-2026-46317, CVE-2026-46325, CVE-2026-53277,\nCVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:11:06Z","modified":"2026-10-17T12:55:29.574386436Z","updated_at":"2026-11-02T16:58:25.103481Z"}]},"sources_more":{"osv":1}}