{"id":"CVE-2026-23138","aliases":["AZL-77703","BELL-CVE-2026-23138","CLSA-2026-1782155469","CLSA-2026-1783791447","DEBIAN-CVE-2026-23138","EUVD-2026-5899","GHSA-gqpg-53jh-cpqf","OESA-2026-1569","OESA-2026-1759","OESA-2026-1760","OESA-2026-1761","OESA-2026-2582","ROOT-OS-DEBIAN-11-CVE-2026-23138","ROOT-OS-DEBIAN-12-CVE-2026-23138","ROOT-OS-UBUNTU-2204-CVE-2026-23138","ROOT-OS-UBUNTU-2404-CVE-2026-23138","SUSE-SU-2026:21230-1","SUSE-SU-2026:21237-1","SUSE-SU-2026:21352-1","SUSE-SU-2026:21361-1","UBUNTU-CVE-2026-23138","USN-8567-1","USN-8570-1","USN-8570-2","USN-8574-1","USN-8574-2","USN-8574-3","USN-8594-1","USN-8595-1","USN-8595-2","USN-8595-3","USN-8596-1","USN-8604-1","USN-8605-1","USN-8606-1","USN-8607-1","USN-8608-1","USN-8609-1","USN-8619-1","USN-8665-1","USN-8669-1","openSUSE-SU-2026:20572-1"],"status":"published","title":"tracing: Add recursion protection in kernel stack trace recording","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","severity":{"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","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00146,"percentile":0.03878,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-02-14T15:22:23Z","modified":"2026-11-10T02:49:49Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.130.1-3"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.191-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.80-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.191","6.6.130","6.12.78","6.18.6"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.85-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:22.04","package":"linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1061.64~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1063.71~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1062.69~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1064.72~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-136.136~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1061.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-136.136.2~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1059.62~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1058.61~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-136.136~22.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1056.57~22.04.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-136.136"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1061.64"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1063.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-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-1062.69"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1064.72"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-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-1059.67"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1046.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-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-1061.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-136.136.2"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1059.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-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-1059.62.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1030.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-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-1058.61"],"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-1061.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","fixed_in":["6.8.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1033.34"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1028.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2050.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1056.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro: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-1061.64+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1063.71+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-136.136+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1064.72+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130.1-3"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.189-r0"},{"fixed":"6.1.191-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.74-r0"},{"fixed":"6.12.80-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els5"}]}],"bundled":141},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els8"}]}],"bundled":305},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.8.0"},{"fixed":"6.1.191"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.78"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.6"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.170-1","6.1.170-2","6.1.170-3","6.1.172-1","6.1.174-1","6.1.176-1","6.1.177-1","6.1.180-1","6.1.187-1","6.1.190-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1","6.10-1~exp1","6.10.1-1~exp1","6.10.11-1","6.10.11-1~bpo12+1","6.10.12-1","6.10.3-1","6.10.4-1","6.10.6-1","6.10.6-1~bpo12+1","6.10.7-1","6.10.9-1","6.11-1~exp1","6.11.10-1","6.11.10-1~bpo12+1","6.11.2-1","6.11.4-1","6.11.5-1","6.11.5-1~bpo12+1","6.11.6-1","6.11.7-1","6.11.9-1","6.11~rc4-1~exp1","6.11~rc5-1~exp1","6.12.10-1","6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.11-1","6.12.11-1+alpha","6.12.11-1+alpha.1","6.12.111-1","6.12.113-1","6.12.115-1","6.12.115-2","6.12.12-1","6.12.12-1~bpo12+1","6.12.13-1","6.12.15-1","6.12.16-1","6.12.17-1","6.12.19-1","6.12.20-1","6.12.21-1","6.12.22-1","6.12.22-1~bpo12+1","6.12.25-1","6.12.27-1","6.12.27-1~bpo12+1","6.12.29-1","6.12.3-1","6.12.30-1","6.12.30-1~bpo12+1","6.12.31-1","6.12.32-1","6.12.32-1~bpo12+1","6.12.33-1","6.12.33-1~bpo12+1","6.12.35-1","6.12.35-1~bpo12+1","6.12.37-1","6.12.38-1","6.12.38-1~bpo12+1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.5-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.6-1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.8-1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.9-1","6.12.9-1+alpha","6.12.9-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.12~rc6-1~exp1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.10-1","6.18.12-1","6.18.12-1~bpo13+1","6.18.13-1","6.18.14-1","6.18.15-1","6.18.15-1~bpo13+1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18.8-1","6.18.9-1","6.18.9-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1","6.19-1~exp1","6.19.10-1","6.19.10-1~bpo13+1","6.19.11-1","6.19.11-1~bpo13+1","6.19.12-1","6.19.13-1","6.19.13-1~bpo13+1","6.19.14-1","6.19.14-1~bpo13+1","6.19.2-1~exp1","6.19.3-1~exp1","6.19.4-1~exp1","6.19.5-1~exp1","6.19.6-1","6.19.6-2","6.19.6-2~bpo13+1","6.19.8-1","6.19.8-1~bpo13+1","6.19~rc4-1~exp1","6.19~rc5-1~exp1","6.19~rc6-1~exp1","6.19~rc7-1~exp1","6.19~rc8-1~exp1","6.3.1-1~exp1","6.3.11-1","6.3.2-1~exp1","6.3.4-1~exp1","6.3.5-1~exp1","6.3.7-1","6.3.7-1~bpo12+1","6.4.1-1~exp1","6.4.11-1","6.4.13-1","6.4.4-1","6.4.4-1~bpo12+1","6.4.4-2","6.4.4-3","6.4.4-3~bpo12+1","6.4~rc6-1~exp1","6.4~rc7-1~exp1","6.5.1-1~exp1","6.5.10-1","6.5.10-1~bpo12+1","6.5.13-1","6.5.3-1","6.5.3-1~bpo12+1","6.5.6-1","6.5.8-1","6.5~rc4-1~exp1","6.5~rc6-1~exp1","6.5~rc7-1~exp1","6.6.11-1","6.6.13-1","6.6.13-1~bpo12+1","6.6.15-1","6.6.15-2","6.6.3-1~exp1","6.6.4-1~exp1","6.6.7-1~exp1","6.6.8-1","6.6.9-1","6.7-1~exp1","6.7.1-1~exp1","6.7.12-1","6.7.12-1~bpo12+1","6.7.4-1~exp1","6.7.7-1","6.7.9-1","6.7.9-2","6.8.11-1","6.8.12-1","6.8.12-1~bpo12+1","6.8.9-1","6.9.10-1","6.9.10-1~bpo12+1","6.9.11-1","6.9.12-1","6.9.2-1~exp1","6.9.7-1","6.9.7-1~bpo12+1","6.9.8-1","6.9.9-1","7.0-1~exp1","7.0.1-1~exp1","7.0.10-1","7.0.10-1~bpo13+1","7.0.12-1","7.0.12-2","7.0.12-2~bpo13+1","7.0.13-1","7.0.13-1~bpo13+1","7.0.14-1","7.0.3-1","7.0.4-1","7.0.4-1~bpo13+1","7.0.7-1","7.0.7-1~bpo13+1","7.0.9-1","7.0.9-1~bpo13+1","7.1.1-1~exp1","7.1.10-1","7.1.12-1","7.1.13-1","7.1.13-1~bpo13+1","7.1.2-1~exp1","7.1.3-1","7.1.3-1+sunvdc","7.1.3-1~bpo13+1","7.1.4-1","7.1.5-1","7.1.6-1","7.1.7-1","7.1.7-1~bpo13+1","7.1.8-1","7.1.8-1~bpo13+1","7.1.8-2","7.1.9-1","7.1.9-1+sparc64","7.1~rc2-1~exp1","7.1~rc3-1~exp1","7.1~rc4-1~exp1","7.1~rc4-1~exp2","7.1~rc5-1~exp1","7.1~rc7-1~exp1","7.2.10-1","7.2.11-1","7.2.11-1~bpo13+1","7.2.12-1","7.2.13-1","7.2.14-1","7.2.15-1","7.2.2-1~exp1","7.2.3-1~exp1","7.2.6-1","7.2.6-1~bpo13+1","7.2.7-1","7.2.8-1","7.2.9-1","7.2.9-1~bpo13+1","7.2~rc3-1~exp1","7.2~rc5-1~exp1","7.2~rc7-1~exp1","7.3.1-1~exp1","7.3~rc6-1~exp1","7.3~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.85-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.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.113-1","6.12.115-1","6.12.115-2","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.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":"openEuler:22.03-LTS-SP4","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-304.0.0.207.oe2203sp4"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.127.oe2403"}]}],"bundled":85},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.139.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.140.oe2403sp2"}]}],"bundled":85},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.3.14.145.oe2403sp3"}]}],"bundled":150},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"gdk-pixbuf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.42.12-160000.4.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-4.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1045.48","4.15.0-1046.49","4.15.0-1048.51","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.55","4.15.0-1055.58","4.15.0-1057.60","4.15.0-1058.61","4.15.0-1059.62","4.15.0-1063.66","4.15.0-1064.67","4.15.0-1066.69","4.15.0-1067.70","4.15.0-1069.72","4.15.0-1070.73","4.15.0-1072.76","4.15.0-1073.78","4.15.0-1074.79","4.15.0-1076.81","4.15.0-1077.82","4.15.0-1078.83","4.15.0-1079.84"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gke-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1025.25~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.31~18.04.1","5.4.0-1030.32~18.04.1","5.4.0-1032.34~18.04.1","5.4.0-1033.35~18.04.1","5.4.0-1035.37~18.04.1","5.4.0-1036.38~18.04.1","5.4.0-1037.39~18.04.1","5.4.0-1039.41~18.04.1","5.4.0-1040.42~18.04.1","5.4.0-1042.44~18.04.1","5.4.0-1043.45~18.04.1","5.4.0-1044.46~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1","5.4.0-1052.55~18.04.1","5.4.0-1053.56~18.04.1","5.4.0-1054.57~18.04.1","5.4.0-1055.58~18.04.1","5.4.0-1056.59~18.04.1","5.4.0-1057.60~18.04.1","5.4.0-1059.62~18.04.1","5.4.0-1061.64~18.04.1","5.4.0-1062.65~18.04.1","5.4.0-1063.66~18.04.1","5.4.0-1065.68~18.04.1","5.4.0-1066.69~18.04.1","5.4.0-1067.70~18.04.1","5.4.0-1068.71~18.04.1","5.4.0-1071.76~18.04.3","5.4.0-1072.77~18.04.1","5.4.0-1074.79~18.04.1","5.4.0-1076.82~18.04.1","5.4.0-1078.84~18.04.1","5.4.0-1080.86~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gkeop-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1001.1","5.4.0-1003.3","5.4.0-1004.5","5.4.0-1005.6","5.4.0-1007.8~18.04.1","5.4.0-1008.9~18.04.1","5.4.0-1009.10~18.04.1","5.4.0-1010.11~18.04.1","5.4.0-1011.12~18.04.2","5.4.0-1012.13~18.04.1","5.4.0-1013.14~18.04.1","5.4.0-1014.15~18.04.1","5.4.0-1015.16~18.04.1","5.4.0-1016.17~18.04.1","5.4.0-1018.19~18.04.1","5.4.0-1021.22~18.04.1","5.4.0-1022.23~18.04.1","5.4.0-1023.24~18.04.1","5.4.0-1024.25~18.04.1","5.4.0-1025.26~18.04.1","5.4.0-1026.27~18.04.1","5.4.0-1027.28~18.04.1","5.4.0-1029.30~18.04.2","5.4.0-1031.32~18.04.1","5.4.0-1032.33~18.04.1","5.4.0-1033.34~18.04.1","5.4.0-1034.35~18.04.1","5.4.0-1036.37~18.04.1","5.4.0-1037.38~18.04.1","5.4.0-1038.39~18.04.1","5.4.0-1039.40~18.04.1","5.4.0-1040.41~18.04.1","5.4.0-1043.44~18.04.1","5.4.0-1046.48~18.04.1","5.4.0-1048.51~18.04.1","5.4.0-1049.52~18.04.1","5.4.0-1051.54~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-13.14~18.04.1","4.18.0-14.15~18.04.1","4.18.0-15.16~18.04.1","4.18.0-16.17~18.04.1","4.18.0-17.18~18.04.1","4.18.0-18.19~18.04.1","4.18.0-20.21~18.04.1","4.18.0-21.22~18.04.1","4.18.0-22.23~18.04.1","4.18.0-24.25~18.04.1","4.18.0-25.26~18.04.1","5.0.0-23.24~18.04.1","5.0.0-25.26~18.04.1","5.0.0-27.28~18.04.1","5.0.0-29.31~18.04.1","5.0.0-31.33~18.04.1","5.0.0-32.34~18.04.2","5.0.0-35.38~18.04.1","5.0.0-36.39~18.04.1","5.0.0-37.40~18.04.1","5.3.0-26.28~18.04.1","5.3.0-28.30~18.04.1","5.3.0-40.32~18.04.1","5.3.0-42.34~18.04.1","5.3.0-45.37~18.04.1","5.3.0-46.38~18.04.1","5.3.0-51.44~18.04.2","5.3.0-53.47~18.04.1","5.3.0-59.53~18.04.1","5.3.0-61.55~18.04.1","5.3.0-62.56~18.04.1","5.3.0-64.58~18.04.1","5.3.0-65.59","5.3.0-66.60","5.3.0-67.61","5.3.0-68.63","5.3.0-69.65","5.3.0-70.66","5.3.0-72.68","5.3.0-73.69","5.3.0-74.70","5.3.0-75.71","5.3.0-76.72"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-15.16~18.04.1","5.0.0-16.17~18.04.1","5.0.0-17.18~18.04.1","5.0.0-19.20~18.04.1","5.0.0-20.21~18.04.1","5.3.0-19.20~18.04.2","5.3.0-22.24~18.04.1","5.3.0-23.25~18.04.1","5.3.0-23.25~18.04.2","5.3.0-24.26~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1014.18~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1017.21~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.24~20.04.1","5.15.0-1021.25~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.1","5.15.0-1037.41~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1","5.15.0-1040.45~20.04.1","5.15.0-1041.46~20.04.1","5.15.0-1043.48~20.04.1","5.15.0-1044.49~20.04.1","5.15.0-1045.50~20.04.1","5.15.0-1047.52~20.04.1","5.15.0-1048.53~20.04.1","5.15.0-1049.54~20.04.1","5.15.0-1050.55~20.04.1","5.15.0-1051.56~20.04.1","5.15.0-1052.57~20.04.1","5.15.0-1053.58~20.04.1","5.15.0-1055.60~20.04.1","5.15.0-1056.61~20.04.1","5.15.0-1057.63~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1075.82~20.04.1","5.15.0-1077.84~20.04.1","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~20.04.1","5.15.0-1103.110~20.04.1","5.15.0-1104.111~20.04.1","5.15.0-1105.112~20.04.1","5.15.0-1106.113~20.04.1","5.15.0-1108.115~20.04.1","5.15.0-1109.116~20.04.1","5.15.0-1111.118~20.04.1","5.15.0-1112.119~20.04.1","5.15.0-1114.121~20.04.1","5.15.0-1115.122~20.04.1","5.15.0-1116.123~20.04.1","5.15.0-1117.124~20.04.1","5.15.0-1119.126~20.04.1","5.15.0-1120.127~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.8~20.04.1","5.15.0-1008.9~20.04.1","5.15.0-1013.16~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1017.20~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.29~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1033.40~20.04.1","5.15.0-1034.41~20.04.1","5.15.0-1035.42~20.04.1","5.15.0-1036.43~20.04.1","5.15.0-1037.44~20.04.1","5.15.0-1038.45~20.04.1","5.15.0-1039.46~20.04.1","5.15.0-1040.47~20.04.1","5.15.0-1041.48~20.04.1","5.15.0-1042.49~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1056.64~20.04.1","5.15.0-1057.65~20.04.1","5.15.0-1058.66~20.04.2","5.15.0-1059.67~20.04.1","5.15.0-1060.69~20.04.1","5.15.0-1061.70~20.04.1","5.15.0-1063.72~20.04.1","5.15.0-1064.73~20.04.1","5.15.0-1065.74~20.04.1","5.15.0-1067.76~20.04.1","5.15.0-1068.77~20.04.1","5.15.0-1070.79~20.04.1","5.15.0-1071.80~20.04.1","5.15.0-1072.81~20.04.1","5.15.0-1073.82~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1079.88~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1110.119~20.04.1","5.15.0-1111.120~20.04.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1123.132~20.04.1","5.15.0-1125.134~20.04.1","5.15.0-1126.135~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1","5.15.0-1081.90~20.04.1.1","5.15.0-1082.91~20.04.1.1","5.15.0-1086.95~20.04.1.1","5.15.0-1087.96~20.04.1.1","5.15.0-1088.97~20.04.1.1","5.15.0-1089.98~20.04.1.1","5.15.0-1091.100~20.04.1.1","5.15.0-1094.103~20.04.1.1","5.15.0-1096.105~20.04.1.1","5.15.0-1097.106~20.04.1.1","5.15.0-1098.107~20.04.1.1","5.15.0-1102.111~20.04.1.1","5.15.0-1103.112~20.04.1.1","5.15.0-1111.120~20.04.1.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.2","5.15.0-1118.127~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1120.129~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1124.133~20.04.1","5.15.0-1125.134~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.9~20.04.1","5.15.0-1012.17~20.04.1","5.15.0-1013.18~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.23~20.04.2","5.15.0-1018.24~20.04.1","5.15.0-1021.28~20.04.1","5.15.0-1022.29~20.04.1","5.15.0-1025.32~20.04.2","5.15.0-1026.33~20.04.1","5.15.0-1027.34~20.04.1","5.15.0-1029.36~20.04.1","5.15.0-1030.37~20.04.1","5.15.0-1031.38~20.04.1","5.15.0-1032.40~20.04.1","5.15.0-1033.41~20.04.1","5.15.0-1034.42~20.04.1","5.15.0-1035.43~20.04.1","5.15.0-1036.44~20.04.1","5.15.0-1037.45~20.04.1","5.15.0-1038.46~20.04.1","5.15.0-1039.47~20.04.1","5.15.0-1040.48~20.04.1","5.15.0-1041.49~20.04.1","5.15.0-1042.50~20.04.1","5.15.0-1044.52~20.04.1","5.15.0-1045.53~20.04.2","5.15.0-1046.54~20.04.1","5.15.0-1047.55~20.04.1","5.15.0-1048.56~20.04.1","5.15.0-1049.57~20.04.1","5.15.0-1051.59~20.04.1","5.15.0-1052.60~20.04.1","5.15.0-1053.61~20.04.1","5.15.0-1054.62~20.04.1","5.15.0-1055.63~20.04.1","5.15.0-1058.66~20.04.1","5.15.0-1059.67~20.04.1","5.15.0-1060.68~20.04.1","5.15.0-1062.70~20.04.1","5.15.0-1065.73~20.04.1","5.15.0-1066.74~20.04.1","5.15.0-1067.75~20.04.1","5.15.0-1068.76~20.04.1","5.15.0-1069.77~20.04.1","5.15.0-1070.78~20.04.1","5.15.0-1071.79~20.04.1","5.15.0-1072.80~20.04.1","5.15.0-1073.81~20.04.1","5.15.0-1074.83~20.04.1","5.15.0-1075.84~20.04.1","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1","5.15.0-1103.112~20.04.1","5.15.0-1104.113~20.04.1","5.15.0-1106.115~20.04.1","5.15.0-1108.117~20.04.1","5.15.0-1109.118~20.04.1","5.15.0-1111.121~20.04.1","5.15.0-1112.122~20.04.1","5.15.0-1114.124~20.04.1","5.15.0-1118.128~20.04.1","5.15.0-1120.130~20.04.1","5.15.0-1121.131~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-41.44~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-57.63~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.86~20.04.2","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.96~20.04.1","5.15.0-87.97~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-130.140~20.04.1","5.15.0-131.141~20.04.1","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-176.186~20.04.1","5.15.0-177.187~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-185.195~20.04.1","5.15.0-186.196~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-198.208~20.04.1","5.15.0-202.212~20.04.1","5.15.0-203.213~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1033.36~20.04.1","5.15.0-1034.37~20.04.1","5.15.0-1035.38~20.04.1","5.15.0-1036.39~20.04.1","5.15.0-1037.40~20.04.1","5.15.0-1038.41~20.04.1","5.15.0-1040.43~20.04.1","5.15.0-1041.44~20.04.1","5.15.0-1042.45~20.04.1","5.15.0-1043.46~20.04.1","5.15.0-1044.47~20.04.1","5.15.0-1045.48~20.04.1","5.15.0-1046.49~20.04.1","5.15.0-1047.50~20.04.1","5.15.0-1048.51~20.04.1","5.15.0-1049.52~20.04.1","5.15.0-1050.53~20.04.1","5.15.0-1053.56~20.04.1","5.15.0-1054.57~20.04.1","5.15.0-1055.58~20.04.1","5.15.0-1057.60~20.04.1","5.15.0-1058.61~20.04.1","5.15.0-1059.62~20.04.1","5.15.0-1060.63~20.04.1","5.15.0-1061.64~20.04.1","5.15.0-1062.65~20.04.1","5.15.0-1063.66~20.04.1","5.15.0-1064.67~20.04.1","5.15.0-1065.68~20.04.1","5.15.0-1066.69~20.04.1","5.15.0-1067.70~20.04.1","5.15.0-1068.71~20.04.1","5.15.0-1069.72~20.04.1","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1","5.15.0-1097.100~20.04.1","5.15.0-1098.101~20.04.1","5.15.0-1099.102~20.04.1","5.15.0-1100.103~20.04.1","5.15.0-1102.105~20.04.1","5.15.0-1103.106~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.1","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1099.105~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1103.109~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1107.113~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1112.118~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1115.121~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-33.34~20.04.1","5.15.0-42.45~20.04.1","5.15.0-43.46~20.04.1","5.15.0-46.49~20.04.1","5.15.0-48.54~20.04.1","5.15.0-50.56~20.04.1","5.15.0-52.58~20.04.1","5.15.0-53.59~20.04.1","5.15.0-56.62~20.04.1","5.15.0-58.64~20.04.1","5.15.0-60.66~20.04.1","5.15.0-67.74~20.04.1","5.15.0-69.76~20.04.1","5.15.0-70.77~20.04.1","5.15.0-71.78~20.04.1","5.15.0-72.79~20.04.1","5.15.0-73.80~20.04.1","5.15.0-75.82~20.04.1","5.15.0-76.83~20.04.1","5.15.0-78.85~20.04.1","5.15.0-79.88~20.04.1","5.15.0-82.91~20.04.1","5.15.0-83.92~20.04.1","5.15.0-84.93~20.04.1","5.15.0-86.95~20.04.1","5.15.0-87.96~20.04.1","5.15.0-88.98~20.04.1","5.15.0-89.99~20.04.1","5.15.0-91.101~20.04.1","5.15.0-92.102~20.04.1","5.15.0-94.104~20.04.1","5.15.0-97.107~20.04.1","5.15.0-100.110~20.04.1","5.15.0-101.111~20.04.1","5.15.0-102.112~20.04.1","5.15.0-105.115~20.04.1","5.15.0-106.116~20.04.1","5.15.0-107.117~20.04.1","5.15.0-110.120~20.04.1","5.15.0-113.123~20.04.1","5.15.0-116.126~20.04.1","5.15.0-117.127~20.04.1","5.15.0-118.128~20.04.1","5.15.0-119.129~20.04.1","5.15.0-121.131~20.04.1","5.15.0-122.132~20.04.1","5.15.0-124.134~20.04.1","5.15.0-125.135~20.04.1","5.15.0-126.136~20.04.1","5.15.0-127.137~20.04.1","5.15.0-128.138~20.04.1","5.15.0-129.139~20.04.1","5.15.0-131.141~20.04.1","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1","5.15.0-173.183~20.04.1","5.15.0-174.184~20.04.1","5.15.0-175.185~20.04.1","5.15.0-177.187~20.04.1","5.15.0-178.188~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-183.193~20.04.1","5.15.0-184.194~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-195.205~20.04.1","5.15.0-197.207~20.04.1","5.15.0-198.208~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9~20.04.1","5.15.0-1010.10~20.04.1","5.15.0-1012.12~20.04.1","5.15.0-1014.14~20.04.1","5.15.0-1015.15~20.04.1","5.15.0-1016.16~20.04.1","5.15.0-1017.17~20.04.1","5.15.0-1018.18~20.04.1","5.15.0-1019.19~20.04.1","5.15.0-1020.20~20.04.1","5.15.0-1022.22~20.04.1","5.15.0-1025.25~20.04.1","5.15.0-1027.27~20.04.1","5.15.0-1030.30~20.04.1","5.15.0-1032.32~20.04.1","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~20.04.1","5.15.0-1055.55~20.04.1","5.15.0-1057.57~20.04.1","5.15.0-1058.58~20.04.1","5.15.0-1060.60~20.04.1","5.15.0-1061.61~20.04.1","5.15.0-1063.63~20.04.1","5.15.0-1064.66~20.04.1","5.15.0-1065.67~20.04.1","5.15.0-1066.68~20.04.1","5.15.0-1067.69~20.04.1","5.15.0-1068.70~20.04.1","5.15.0-1070.72~20.04.1","5.15.0-1071.73~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1007.9~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1016.20~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1021.27~20.04.1","5.15.0-1022.28~20.04.1","5.15.0-1025.31~20.04.2","5.15.0-1027.33~20.04.1","5.15.0-1029.35~20.04.1","5.15.0-1030.36~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1041.47~20.04.1","5.15.0-1042.48~20.04.1","5.15.0-1044.50~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1047.53~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1053.59~20.04.1","5.15.0-1054.60~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~20.04.1","5.15.0-1068.74~20.04.1","5.15.0-1069.75~20.04.1","5.15.0-1070.76~20.04.1","5.15.0-1071.77~20.04.1","5.15.0-1072.78~20.04.1","5.15.0-1073.79~20.04.1","5.15.0-1074.80~20.04.1","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1102.108~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1116.122~20.04.1","5.15.0-1117.123~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1015.17~20.04.1","5.15.0-1017.19~20.04.1","5.15.0-1018.21~20.04.1","5.15.0-1019.22~20.04.1","5.15.0-1022.26~20.04.1","5.15.0-1023.27~20.04.1","5.15.0-1026.30~20.04.2","5.15.0-1027.31~20.04.1","5.15.0-1028.32~20.04.1","5.15.0-1029.33~20.04.1","5.15.0-1030.34~20.04.1","5.15.0-1031.35~20.04.1","5.15.0-1032.36~20.04.1","5.15.0-1033.37~20.04.1","5.15.0-1034.38~20.04.1","5.15.0-1035.39~20.04.1","5.15.0-1036.40~20.04.2","5.15.0-1037.41~20.04.2","5.15.0-1038.42~20.04.2","5.15.0-1039.43~20.04.2","5.15.0-1040.44~20.04.3","5.15.0-1041.45~20.04.1","5.15.0-1043.47~20.04.1","5.15.0-1044.48~20.04.1","5.15.0-1045.49~20.04.1","5.15.0-1046.50~20.04.1","5.15.0-1047.51~20.04.1","5.15.0-1048.52~20.04.1","5.15.0-1049.53~20.04.2","5.15.0-1050.54~20.04.1","5.15.0-1051.55~20.04.1","5.15.0-1052.56~20.04.1","5.15.0-1053.57~20.04.1","5.15.0-1056.60~20.04.1","5.15.0-1057.61~20.04.1","5.15.0-1058.62~20.04.1","5.15.0-1059.63~20.04.1","5.15.0-1060.64~20.04.1","5.15.0-1061.65~20.04.1","5.15.0-1062.66~20.04.1","5.15.0-1063.67~20.04.1","5.15.0-1064.68~20.04.1","5.15.0-1065.69~20.04.1","5.15.0-1066.70~20.04.1","5.15.0-1067.71~20.04.1","5.15.0-1068.72~20.04.1","5.15.0-1069.73~20.04.1","5.15.0-1070.74~20.04.1","5.15.0-1071.75~20.04.1","5.15.0-1072.76~20.04.1","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1","5.15.0-1097.101~20.04.1","5.15.0-1098.102~20.04.1","5.15.0-1099.103~20.04.1","5.15.0-1100.104~20.04.1","5.15.0-1102.106~20.04.1","5.15.0-1103.107~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.2","5.15.0-1114.118~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-19.19","5.15.0-17.17","5.15.0-18.18","5.15.0-22.22","5.15.0-23.23","5.15.0-25.25","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.51","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.86","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.96","5.15.0-87.97","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-112.122","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-130.140","5.15.0-131.141","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-176.186","5.15.0-177.187","5.15.0-179.189","5.15.0-181.191","5.15.0-185.195","5.15.0-186.196","5.15.0-187.197","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-198.208","5.15.0-202.212","5.15.0-203.213"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-allwinner-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1007.7~22.04.1","5.19.0-1009.9~22.04.1","5.19.0-1010.10~22.04.1","5.19.0-1011.11~22.04.1","5.19.0-1012.12~22.04.1","5.19.0-1013.13~22.04.1","5.19.0-1014.14~22.04.1","5.19.0-1015.15~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1008.10","5.15.0-1009.11","5.15.0-1011.14","5.15.0-1013.17","5.15.0-1014.18","5.15.0-1015.19","5.15.0-1017.21","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.25","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1033.37","5.15.0-1034.38","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1055.60","5.15.0-1056.61","5.15.0-1057.63","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1076.83","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108","5.15.0-1103.110","5.15.0-1104.111","5.15.0-1105.112","5.15.0-1106.113","5.15.0-1108.115","5.15.0-1109.116","5.15.0-1111.118","5.15.0-1112.119","5.15.0-1113.120","5.15.0-1114.121","5.15.0-1115.122","5.15.0-1116.123","5.15.0-1117.124","5.15.0-1119.126","5.15.0-1120.127"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1057.60~22.04.1","6.8.0-1060.63~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1006.7","5.15.0-1001.2","5.15.0-1002.3","5.15.0-1003.4","5.15.0-1005.6","5.15.0-1007.8","5.15.0-1008.9","5.15.0-1010.12","5.15.0-1012.15","5.15.0-1013.16","5.15.0-1014.17","5.15.0-1017.20","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.29","5.15.0-1024.30","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1033.40","5.15.0-1034.41","5.15.0-1035.42","5.15.0-1036.43","5.15.0-1037.44","5.15.0-1038.45","5.15.0-1039.46","5.15.0-1040.47","5.15.0-1041.48","5.15.0-1042.49","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1056.64","5.15.0-1057.65","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.69","5.15.0-1061.70","5.15.0-1063.72","5.15.0-1064.73","5.15.0-1066.75","5.15.0-1067.76","5.15.0-1068.77","5.15.0-1070.79","5.15.0-1071.80","5.15.0-1072.81","5.15.0-1073.82","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1109.118","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1123.132","5.15.0-1125.134","5.15.0-1126.135"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1","6.8.0-1059.65~22.04.1","6.8.0-1062.69~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24.1","5.15.0-1024.30.1","5.15.0-1029.36.1","5.15.0-1030.37.1","5.15.0-1031.38.1","5.15.0-1033.40.1","5.15.0-1034.41.1","5.15.0-1035.42.1","5.15.0-1036.43.1","5.15.0-1037.44.1","5.15.0-1038.45.1","5.15.0-1039.46.1","5.15.0-1041.48.1","5.15.0-1042.49.1","5.15.0-1044.51.1","5.15.0-1045.52.1","5.15.0-1046.53.1","5.15.0-1047.54.1","5.15.0-1049.56.1","5.15.0-1050.57.1","5.15.0-1051.59.1","5.15.0-1052.60.1","5.15.0-1053.61.1","5.15.0-1054.62.1","5.15.0-1056.64.1","5.15.0-1057.65.1","5.15.0-1058.66.1","5.15.0-1059.67.1","5.15.0-1060.69.1","5.15.0-1061.70.1","5.15.0-1063.72.1","5.15.0-1064.73.1","5.15.0-1065.74.1","5.15.0-1067.76.1","5.15.0-1068.77.1","5.15.0-1070.79.1","5.15.0-1071.80.1","5.15.0-1072.81.1","5.15.0-1073.82.1","5.15.0-1076.85.1","5.15.0-1078.87.1","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.1","5.15.0-1109.118.1","5.15.0-1110.119.1","5.15.0-1111.120.1","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1120.129","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1124.133","5.15.0-1125.134"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1025.28~22.04.1.1","5.19.0-1026.29~22.04.1.1","5.19.0-1027.30~22.04.2.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1.1","6.2.0-1009.9~22.04.3.1","6.2.0-1011.11~22.04.1.1","6.2.0-1012.12~22.04.1.1","6.2.0-1014.14~22.04.1.1","6.2.0-1015.15~22.04.1.1","6.2.0-1016.16~22.04.1.1","6.2.0-1017.17~22.04.1.1","6.2.0-1018.18~22.04.1.1","6.2.0-1019.19~22.04.1.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1","6.8.0-1058.65~22.04.1","6.8.0-1061.68~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1005.6","5.15.0-1001.3","5.15.0-1002.5","5.15.0-1003.6","5.15.0-1004.7","5.15.0-1005.8","5.15.0-1006.9","5.15.0-1008.12","5.15.0-1010.15","5.15.0-1013.18","5.15.0-1016.21","5.15.0-1017.23","5.15.0-1018.24","5.15.0-1019.25","5.15.0-1021.28","5.15.0-1022.29","5.15.0-1025.32","5.15.0-1026.33","5.15.0-1027.34","5.15.0-1029.36","5.15.0-1030.37","5.15.0-1031.38","5.15.0-1032.40","5.15.0-1034.42","5.15.0-1035.43","5.15.0-1036.44","5.15.0-1037.45","5.15.0-1038.46","5.15.0-1039.47","5.15.0-1040.48","5.15.0-1041.49","5.15.0-1042.50","5.15.0-1044.52","5.15.0-1045.53","5.15.0-1046.54","5.15.0-1047.55","5.15.0-1048.56","5.15.0-1049.57","5.15.0-1051.59","5.15.0-1052.60","5.15.0-1053.61","5.15.0-1054.62","5.15.0-1055.63","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.83","5.15.0-1075.84","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1106.115","5.15.0-1108.117","5.15.0-1109.118","5.15.0-1111.121","5.15.0-1112.122","5.15.0-1114.124","5.15.0-1115.125","5.15.0-1117.127","5.15.0-1118.128","5.15.0-1120.130","5.15.0-1121.131"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1063.69~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.5","5.15.0-1005.6","5.15.0-1006.7","5.15.0-1008.10","5.15.0-1010.13","5.15.0-1011.14","5.15.0-1014.17","5.15.0-1015.18","5.15.0-1016.19","5.15.0-1017.20","5.15.0-1019.23","5.15.0-1020.25","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1104.110","5.15.0-1105.111","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1115.121","5.15.0-1116.122"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.2","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1004.6","5.15.0-1005.7","5.15.0-1007.10","5.15.0-1008.12","5.15.0-1011.15","5.15.0-1012.16","5.15.0-1013.17","5.15.0-1015.19","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1020.25","5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.37","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.50","5.15.0-1044.51","5.15.0-1045.52","5.15.0-1046.53","5.15.0-1047.54","5.15.0-1048.55","5.15.0-1049.56","5.15.0-1050.57","5.15.0-1051.58","5.15.0-1052.59","5.15.0-1053.60","5.15.0-1054.61","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1059.67","5.15.0-1060.68","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92","5.15.0-1086.94","5.15.0-1087.95","5.15.0-1088.96","5.15.0-1089.97","5.15.0-1091.99","5.15.0-1092.100","5.15.0-1094.102","5.15.0-1095.103","5.15.0-1096.104","5.15.0-1097.105","5.15.0-1098.106","5.15.0-1099.107","5.15.0-1100.108","5.15.0-1102.110","5.15.0-1103.111"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.8","5.15.0-1009.11","5.15.0-1010.12","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1015.17","5.15.0-1017.20","5.15.0-1018.21","5.15.0-1021.24","5.15.0-1022.25","5.15.0-1023.26","5.15.0-1025.28","5.15.0-1026.29","5.15.0-1027.30","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1031.34","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1056.59","5.15.0-1057.60","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1068.71","5.15.0-1069.72","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.109","5.15.0-1106.110","5.15.0-1107.111","5.15.0-1108.112","5.15.0-1109.113","5.15.0-1110.114","5.15.0-1111.115","5.15.0-1113.117","5.15.0-1114.118"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1004.6","5.15.0-1008.11","5.15.0-1010.14","5.15.0-1013.17","5.15.0-1015.20","5.15.0-1016.21","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1021.26","5.15.0-1023.28","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1027.32","5.15.0-1028.33","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1036.41","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1043.49","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1055.61","5.15.0-1057.63","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1098.104","5.15.0-1099.105","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1103.109","5.15.0-1104.110","5.15.0-1106.112","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1114.120","5.15.0-1115.121"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1010.11","5.15.0-1012.14","5.15.0-1013.16","5.15.0-1016.19","5.15.0-1017.21","5.15.0-1018.22","5.15.0-1019.23","5.15.0-1020.24","5.15.0-1021.26","5.15.0-1024.29","5.15.0-1025.30","5.15.0-1026.31","5.15.0-1028.33","5.15.0-1029.34","5.15.0-1030.35","5.15.0-1031.36","5.15.0-1032.37","5.15.0-1033.38","5.15.0-1034.39","5.15.0-1035.40","5.15.0-1037.42","5.15.0-1038.43","5.15.0-1039.44","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.51","5.15.0-1047.52","5.15.0-1048.53","5.15.0-1049.54","5.15.0-1050.55","5.15.0-1051.56","5.15.0-1052.57","5.15.0-1053.58","5.15.0-1054.59","5.15.0-1057.62","5.15.0-1058.63","5.15.0-1059.64","5.15.0-1060.65","5.15.0-1061.66","5.15.0-1062.67","5.15.0-1063.68","5.15.0-1064.69","5.15.0-1065.70","5.15.0-1066.71","5.15.0-1067.72","5.15.0-1068.73","5.15.0-1069.74","5.15.0-1070.75","5.15.0-1071.76","5.15.0-1072.77","5.15.0-1073.78","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98","5.15.0-1095.100","5.15.0-1096.101","5.15.0-1097.102","5.15.0-1098.103","5.15.0-1100.105","5.15.0-1101.106","5.15.0-1103.108","5.15.0-1104.109","5.15.0-1105.110","5.15.0-1106.111","5.15.0-1107.112","5.15.0-1108.113","5.15.0-1109.114","5.15.0-1111.116","5.15.0-1112.117"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-22.22","5.15.0-23.23","5.15.0-24.24","5.15.0-27.28","5.15.0-30.31","5.15.0-33.34","5.15.0-35.36","5.15.0-37.39","5.15.0-39.42","5.15.0-40.43","5.15.0-41.44","5.15.0-43.46","5.15.0-46.49","5.15.0-47.53","5.15.0-48.54","5.15.0-50.56","5.15.0-52.58","5.15.0-53.59","5.15.0-56.62","5.15.0-57.63","5.15.0-58.64","5.15.0-60.66","5.15.0-67.74","5.15.0-69.76","5.15.0-70.77","5.15.0-71.78","5.15.0-72.79","5.15.0-73.80","5.15.0-75.82","5.15.0-76.83","5.15.0-78.85","5.15.0-79.88","5.15.0-82.91","5.15.0-83.92","5.15.0-84.93","5.15.0-86.95","5.15.0-87.96","5.15.0-88.98","5.15.0-89.99","5.15.0-91.101","5.15.0-92.102","5.15.0-94.104","5.15.0-97.107","5.15.0-100.110","5.15.0-101.111","5.15.0-102.112","5.15.0-105.115","5.15.0-106.116","5.15.0-107.117","5.15.0-110.120","5.15.0-113.123","5.15.0-116.126","5.15.0-117.127","5.15.0-118.128","5.15.0-119.129","5.15.0-121.131","5.15.0-122.132","5.15.0-124.134","5.15.0-125.135","5.15.0-126.136","5.15.0-127.137","5.15.0-128.138","5.15.0-129.139","5.15.0-131.141","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181","5.15.0-173.183","5.15.0-174.184","5.15.0-175.185","5.15.0-177.187","5.15.0-178.188","5.15.0-179.189","5.15.0-181.191","5.15.0-183.193","5.15.0-184.194","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-195.205","5.15.0-197.207","5.15.0-198.208"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1","6.8.0-117.117.1~22.04.1","6.8.0-134.134.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1005.5","5.15.0-1007.7","5.15.0-1010.10","5.15.0-1015.15","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1023.23","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1037.37","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1053.54","5.15.0-1054.55","5.15.0-1055.56","5.15.0-1058.59","5.15.0-1059.60","5.15.0-1060.61","5.15.0-1061.62","5.15.0-1062.63","5.15.0-1063.64","5.15.0-1064.65","5.15.0-1065.66","5.15.0-1066.67","5.15.0-1067.68","5.15.0-1068.69","5.15.0-1069.70","5.15.0-1070.71","5.15.0-1071.72","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97","5.15.0-1098.99","5.15.0-1099.100","5.15.0-1100.101","5.15.0-1101.102","5.15.0-1103.104","5.15.0-1104.105","5.15.0-1106.107","5.15.0-1107.108","5.15.0-1108.109","5.15.0-1109.110","5.15.0-1110.111","5.15.0-1111.112","5.15.0-1112.113","5.15.0-1114.115","5.15.0-1115.116"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1009.9","5.15.0-1010.10","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1017.17","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1025.25","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1030.30","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1043.43","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1048.48","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1058.58","5.15.0-1060.60","5.15.0-1061.61","5.15.0-1063.63","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1068.70","5.15.0-1070.72","5.15.0-1071.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1001.1","5.15.0-1002.2","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1009.9","5.15.0-1012.12","5.15.0-1013.13","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1018.18","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","5.15.0-1026.26","5.15.0-1027.27","5.15.0-1028.28","5.15.0-1029.29","5.15.0-1030.30","5.15.0-1031.31","5.15.0-1032.32","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42","5.15.0-1044.44","5.15.0-1045.45","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1054.54","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1059.59"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-5.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.17.0-1003.3","5.17.0-1004.4","5.17.0-1006.6","5.17.0-1011.12","5.17.0-1012.13","5.17.0-1013.14","5.17.0-1014.15","5.17.0-1015.16","5.17.0-1016.17","5.17.0-1017.18","5.17.0-1018.19","5.17.0-1019.20","5.17.0-1020.21","5.17.0-1021.22","5.17.0-1024.25","5.17.0-1025.26","5.17.0-1026.27","5.17.0-1027.28","5.17.0-1028.29","5.17.0-1029.30","5.17.0-1030.31","5.17.0-1031.32","5.17.0-1032.33","5.17.0-1033.34","5.17.0-1034.35","5.17.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.0.0-1006.6","6.0.0-1007.7","6.0.0-1008.8","6.0.0-1009.9","6.0.0-1010.10","6.0.0-1011.11","6.0.0-1012.12","6.0.0-1013.13","6.0.0-1014.14","6.0.0-1015.15","6.0.0-1016.16","6.0.0-1017.17","6.0.0-1018.18","6.0.0-1019.19","6.0.0-1020.20","6.0.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.1.0-1004.4","6.1.0-1006.6","6.1.0-1007.7","6.1.0-1008.8","6.1.0-1009.9","6.1.0-1010.10","6.1.0-1012.12","6.1.0-1013.13","6.1.0-1014.14","6.1.0-1015.15","6.1.0-1016.16","6.1.0-1017.17","6.1.0-1019.19","6.1.0-1020.20","6.1.0-1021.21","6.1.0-1022.22","6.1.0-1023.23","6.1.0-1024.24","6.1.0-1025.25","6.1.0-1026.26","6.1.0-1027.27","6.1.0-1028.28","6.1.0-1029.29","6.1.0-1033.33","6.1.0-1034.34","6.1.0-1035.35","6.1.0-1036.36"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oem-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1003.3","6.5.0-1004.4","6.5.0-1006.6","6.5.0-1007.7","6.5.0-1008.8","6.5.0-1009.10","6.5.0-1011.12","6.5.0-1013.14","6.5.0-1014.15","6.5.0-1015.16","6.5.0-1016.17","6.5.0-1018.19","6.5.0-1019.20","6.5.0-1020.21","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25","6.5.0-1025.26","6.5.0-1027.28"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.10","5.15.0-1001.3","5.15.0-1002.4","5.15.0-1003.5","5.15.0-1006.8","5.15.0-1007.9","5.15.0-1009.12","5.15.0-1011.15","5.15.0-1013.17","5.15.0-1016.20","5.15.0-1017.22","5.15.0-1018.23","5.15.0-1019.24","5.15.0-1021.27","5.15.0-1022.28","5.15.0-1025.31","5.15.0-1026.32","5.15.0-1027.33","5.15.0-1029.35","5.15.0-1030.36","5.15.0-1032.38","5.15.0-1033.39","5.15.0-1034.40","5.15.0-1035.41","5.15.0-1036.42","5.15.0-1037.43","5.15.0-1038.44","5.15.0-1039.45","5.15.0-1040.46","5.15.0-1041.47","5.15.0-1042.48","5.15.0-1044.50","5.15.0-1045.51","5.15.0-1046.52","5.15.0-1047.53","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.61","5.15.0-1058.64","5.15.0-1059.65","5.15.0-1060.66","5.15.0-1061.67","5.15.0-1062.68","5.15.0-1063.69","5.15.0-1064.70","5.15.0-1065.71","5.15.0-1066.72","5.15.0-1067.73","5.15.0-1068.74","5.15.0-1069.75","5.15.0-1070.76","5.15.0-1071.77","5.15.0-1072.78","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1103.109","5.15.0-1105.111","5.15.0-1106.112","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1114.120","5.15.0-1116.122","5.15.0-1117.123"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1","6.8.0-1054.55~22.04.1","6.8.0-1057.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9","5.15.0-1002.2","5.15.0-1003.3","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1008.8","5.15.0-1011.13","5.15.0-1012.14","5.15.0-1013.15","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.20","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1025.27","5.15.0-1026.28","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1029.31","5.15.0-1030.32","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1035.38","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1040.43","5.15.0-1041.44","5.15.0-1042.45","5.15.0-1043.46","5.15.0-1044.47","5.15.0-1045.48","5.15.0-1046.49","5.15.0-1047.50","5.15.0-1048.51","5.15.0-1049.52","5.15.0-1050.53","5.15.0-1053.56","5.15.0-1054.57","5.15.0-1055.58","5.15.0-1058.61","5.15.0-1059.62","5.15.0-1060.63","5.15.0-1061.64","5.15.0-1062.65","5.15.0-1063.66","5.15.0-1064.67","5.15.0-1065.68","5.15.0-1066.69","5.15.0-1067.70","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1097.100","5.15.0-1098.101","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.108","5.15.0-1106.109","5.15.0-1108.111","5.15.0-1110.113"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.3"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1022.26","5.15.0-1023.27","5.15.0-1025.29","5.15.0-1027.31","5.15.0-1030.34","5.15.0-1031.35","5.15.0-1035.39","5.15.0-1036.40","5.15.0-1037.41","5.15.0-1038.42","5.15.0-1039.43","5.15.0-1041.45","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73","5.15.0-1070.74","5.15.0-1074.78","5.15.0-1075.79","5.15.0-1076.80","5.15.0-1077.81","5.15.0-1078.82","5.15.0-1079.83","5.15.0-1080.84"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1017.19","5.15.0-1019.21","5.15.0-1021.23","5.15.0-1022.24","5.15.0-1023.25","5.15.0-1024.26","5.15.0-1027.29","5.15.0-1028.30","5.15.0-1031.33","5.15.0-1032.34","5.15.0-1033.35","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1040.42","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1045.47","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1050.52","5.15.0-1051.53","5.15.0-1052.54","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1095.97","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1021.26","5.15.0-1022.27","5.15.0-1023.28","5.15.0-1024.29","5.15.0-1028.33","5.15.0-1033.35","5.15.0-1034.36","5.15.0-1035.37","5.15.0-1036.38","5.15.0-1037.39","5.15.0-1038.40","5.15.0-1039.41","5.15.0-1040.42","5.15.0-1041.43","5.15.0-1042.44","5.15.0-1043.45","5.15.0-1044.46","5.15.0-1046.48","5.15.0-1047.49","5.15.0-1048.50","5.15.0-1049.51","5.15.0-1050.52","5.15.0-1053.55","5.15.0-1054.56","5.15.0-1055.57","5.15.0-1056.58","5.15.0-1057.59","5.15.0-1058.60","5.15.0-1059.61","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1066.68","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1094.96","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106","5.15.0-1105.107","5.15.0-1106.108","5.15.0-1107.109","5.15.0-1108.110","5.15.0-1109.111","5.15.0-1111.115","5.15.0-1112.116"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1006.6","5.15.0-1007.7","5.15.0-1009.9","5.15.0-1011.11","5.15.0-1014.14","5.15.0-1015.15","5.15.0-1016.16","5.15.0-1019.19","5.15.0-1020.20","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1024.25","5.15.0-1025.28","5.15.0-1028.31","5.15.0-1029.32","5.15.0-1030.33","5.15.0-1032.35","5.15.0-1033.36","5.15.0-1034.37","5.15.0-1036.39","5.15.0-1037.40","5.15.0-1038.41","5.15.0-1039.42","5.15.0-1040.45","5.15.0-1041.46","5.15.0-1042.47","5.15.0-1043.48","5.15.0-1044.49","5.15.0-1045.50","5.15.0-1046.52","5.15.0-1048.54","5.15.0-1049.55","5.15.0-1050.56","5.15.0-1051.57","5.15.0-1052.58","5.15.0-1053.59","5.15.0-1054.60","5.15.0-1055.62","5.15.0-1056.63","5.15.0-1057.64","5.15.0-1058.66","5.15.0-1061.69","5.15.0-1062.70","5.15.0-1063.71","5.15.0-1064.72","5.15.0-1065.73","5.15.0-1066.74","5.15.0-1067.75","5.15.0-1068.76","5.15.0-1069.77","5.15.0-1070.78","5.15.0-1071.79","5.15.0-1072.80","5.15.0-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1077.85","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1102.111","5.15.0-1103.112","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1107.116","5.15.0-1108.117","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1112.121","5.15.0-1113.122","5.15.0-1114.123","5.15.0-1115.124","5.15.0-1116.125","5.15.0-1118.127","5.15.0-1119.128"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57~22.04.2"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1051.56+fips1","5.15.0-1052.57+fips1","5.15.0-1053.58+fips1","5.15.0-1055.60+fips1","5.15.0-1056.61+fips1","5.15.0-1057.63+fips1","5.15.0-1060.66+fips1","5.15.0-1061.67+fips1","5.15.0-1062.68+fips1","5.15.0-1063.69+fips1","5.15.0-1064.70+fips1","5.15.0-1065.71+fips1","5.15.0-1066.72+fips1","5.15.0-1067.73+fips1","5.15.0-1068.74+fips1","5.15.0-1069.75+fips1","5.15.0-1070.76+fips1","5.15.0-1071.77+fips1","5.15.0-1072.78+fips1","5.15.0-1073.79+fips1","5.15.0-1076.83+fips1","5.15.0-1077.84+fips1","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1","5.15.0-1103.110+fips1","5.15.0-1104.111+fips1","5.15.0-1105.112+fips1","5.15.0-1106.113+fips1","5.15.0-1108.115+fips1","5.15.0-1109.116+fips1","5.15.0-1111.118+fips1","5.15.0-1112.119+fips1","5.15.0-1113.120+fips1","5.15.0-1114.121+fips1","5.15.0-1115.122+fips1","5.15.0-1116.123+fips1","5.15.0-1117.124+fips1","5.15.0-1119.126+fips1","5.15.0-1120.127+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.69+fips1","5.15.0-1061.70+fips1","5.15.0-1063.72+fips1","5.15.0-1064.73+fips1","5.15.0-1065.74+fips1","5.15.0-1067.76+fips1","5.15.0-1068.77+fips1","5.15.0-1070.79+fips1","5.15.0-1071.80+fips1","5.15.0-1072.81+fips1","5.15.0-1073.82+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1","5.15.0-1109.118+fips1","5.15.0-1110.119+fips1","5.15.0-1111.120+fips1","5.15.0-1114.123+fips1","5.15.0-1116.125+fips1","5.15.0-1117.126+fips1","5.15.0-1118.127+fips1","5.15.0-1119.128+fips1","5.15.0-1121.130+fips1","5.15.0-1122.131+fips1","5.15.0-1123.132+fips1","5.15.0-1125.134+fips1","5.15.0-1126.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1","5.15.0-92.102+fips1","5.15.0-94.104+fips1","5.15.0-97.107+fips1","5.15.0-100.110+fips1","5.15.0-101.111+fips1","5.15.0-102.112+fips1","5.15.0-105.115+fips1","5.15.0-106.116+fips1","5.15.0-107.117+fips1","5.15.0-111.121+fips1","5.15.0-113.123+fips1","5.15.0-115.125+fips1","5.15.0-117.127+fips1","5.15.0-118.128+fips1","5.15.0-119.129+fips1","5.15.0-121.131+fips1","5.15.0-122.132+fips1","5.15.0-124.134+fips1","5.15.0-125.135+fips1","5.15.0-127.137+fips1","5.15.0-128.138+fips1","5.15.0-130.140+fips1","5.15.0-131.141+fips1","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1","5.15.0-173.183+fips1","5.15.0-174.184+fips1","5.15.0-176.186+fips1","5.15.0-177.187+fips1","5.15.0-179.189+fips1","5.15.0-181.191+fips1","5.15.0-185.195+fips1","5.15.0-186.196+fips1","5.15.0-190.200+fips1","5.15.0-191.201+fips1","5.15.0-194.204+fips1","5.15.0-198.208+fips1","5.15.0-202.212+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1","5.15.0-1055.63+fips2","5.15.0-1058.66+fips1","5.15.0-1059.67+fips1","5.15.0-1060.68+fips1","5.15.0-1062.70+fips1","5.15.0-1063.71+fips1","5.15.0-1064.72+fips1","5.15.0-1065.73+fips1","5.15.0-1066.74+fips1","5.15.0-1067.75+fips1","5.15.0-1068.76+fips1","5.15.0-1069.77+fips1","5.15.0-1070.78+fips1","5.15.0-1071.79+fips1","5.15.0-1072.80+fips1","5.15.0-1073.81+fips1","5.15.0-1074.83+fips1","5.15.0-1075.84+fips1","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1","5.15.0-1105.114+fips1","5.15.0-1106.115+fips1","5.15.0-1108.117+fips1","5.15.0-1109.118+fips1","5.15.0-1111.121+fips1","5.15.0-1112.122+fips1","5.15.0-1114.124+fips1","5.15.0-1115.125+fips1","5.15.0-1116.126+fips1","5.15.0-1118.128+fips1","5.15.0-1120.130+fips1","5.15.0-1121.131+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1019.19~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32","6.8.0-1039.42"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1059.67"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1061.62"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1","6.8.0-117.117.1","6.8.0-134.134.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1059.62.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1058.61"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53","6.8.0-1054.55","6.8.0-1057.58"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1061.65"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-14.14.1~24.04.1","6.17.0-19.19.1~24.04.1","6.17.0-20.20.1~24.04.1","6.17.0-22.22.1~24.04.1","6.17.0-23.23.1~24.04.1","6.17.0-29.29.1~24.04.1","6.17.0-35.35.1~24.04.1","6.17.0-38.38.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1008.8"}]}],"versions":["6.8.0-1005.5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1032.33"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.33"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1026.30"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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-1061.64+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71+fips2"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20","6.17.0-22.22","6.17.0-23.23","6.17.0-29.29","6.17.0-35.35","6.17.0-40.40"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1016.17","6.17.0-1018.19","6.17.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1016.16","6.17.0-1018.18"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1014.14","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10","6.17.0-1010.11","6.17.0-1011.12","6.17.0-1013.15","6.17.0-1014.16","6.17.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1","6.17.0-14.14.1","6.17.0-19.19.1","6.17.0-20.20.1","6.17.0-22.22.1","6.17.0-23.23.1","6.17.0-29.29.1","6.17.0-35.35.1","6.17.0-40.40.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1","6.8.0-1060.63~22.04.1","6.8.0-1063.69~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57~22.04.2"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1","6.8.1-1051.52~22.04.1","6.8.1-1052.53~22.04.1","6.8.1-1055.56~22.04.1"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111","6.8.0-117.117","6.8.0-124.124","6.8.0-134.134"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61","6.8.0-1060.63","6.8.0-1063.69"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.67"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57","6.8.0-1054.60","6.8.0-1055.61","6.8.0-1058.64"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1046.50"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1045.48"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1056.57"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49","6.8.1-1051.52","6.8.1-1052.53","6.8.1-1055.56"],"bundled":891},{"source":"osv","ecosystem":"Ubuntu: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:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1064.72+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1","6.8.0-1058.61+fips1","6.8.0-1060.63+fips1","6.8.0-1063.69+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1","6.8.0-117.117.1~22.04.1","6.8.0-134.134.1~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136.2"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1","6.8.0-117.117.1","6.8.0-134.134.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53","6.8.0-1054.55","6.8.0-1057.58"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1","6.8.0-116.116+fips1","6.8.0-124.124+fips1","6.8.0-134.134+fips1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1","6.8.0-1055.56~22.04.1","6.8.0-1057.58~22.04.1","6.8.0-1060.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.62"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52","6.8.0-1055.56","6.8.0-1057.58","6.8.0-1060.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1030.31"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1029.30"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1033.34"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1032.33"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu: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:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1","6.8.0-1054.55~22.04.1","6.8.0-1057.58~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1055.58","6.8.0-1057.60","6.8.0-1060.63"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1057.60~22.04.1","6.8.0-1060.63~22.04.1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.64+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1055.58+fips1","6.8.0-1057.60+fips1","6.8.0-1060.63+fips1"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1055.58~22.04.1","6.8.0-1058.61~22.04.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1054.57","6.8.0-1055.58","6.8.0-1058.61"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.62.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1","6.8.0-1054.57.1","6.8.0-1055.58.1","6.8.0-1058.61.1"],"bundled":913},{"source":"osv","ecosystem":"Ubuntu: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:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1","6.8.0-1059.65~22.04.1","6.8.0-1062.69~22.04.1"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60","6.8.0-1056.62","6.8.0-1058.64","6.8.0-1059.65","6.8.0-1062.69"],"bundled":1210},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60","6.8.0-1058.65","6.8.0-1061.68"],"bundled":1205},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1063.71+fips2"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1","6.8.0-1059.65+fips1","6.8.0-1062.69+fips1"],"bundled":914},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1062.69~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1","6.8.0-1058.65~22.04.1","6.8.0-1061.68~22.04.1"],"bundled":1206},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-136.136~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1","6.8.0-124.124~22.04.1","6.8.0-134.134~22.04.1"],"bundled":1209},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1061.65"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57","6.8.0-1056.60","6.8.0-1057.61","6.8.0-1060.64"],"bundled":912},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2050.52"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44","6.8.0-2045.46","6.8.0-2046.47","6.8.0-2049.50"],"bundled":912},{"source":"osv","ecosystem":"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.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.28.1"}]}],"bundled":49}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://git.kernel.org/stable/c/80fe242a6239778025ba3be8e7263e3d69c37947","tags":["web"]},{"url":"https://git.kernel.org/stable/c/9b03768037d91ce727effb1c5d92d2c7781bf692","tags":["web"]},{"url":"https://git.kernel.org/stable/c/19e18e6dabb1bbba76d2809ca7d8ae9e1f5975fe","tags":["web"]},{"url":"https://git.kernel.org/stable/c/5b7f91acffd2c4c000971553d22efa1e1bb4feae","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/5f1ef0dfcb5b7f4a91a9b0e0ba533efd9f7e2cdb","tags":["Patch","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-gqpg-53jh-cpqf"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23138","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1782155469.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-3633","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50521","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42290","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43835","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21870","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37914","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38048","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38460","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39721","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-54505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68820","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71077","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-71087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71095","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-71099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71132","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71227","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-2025-71273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23066","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23210","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23357","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23381","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23382","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23455","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31497","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31512","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31515","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31521","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31602","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31634","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43158","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43332","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46317","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1783791447.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-4454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-1462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49443","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49728","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49749","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49825","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49873","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52523","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52845","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52898","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53002","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53018","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53026","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53291","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53332","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53517","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53635","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53792","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53857","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54254","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26645","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26837","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26862","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26906","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36008","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36882","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36975","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38598","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38600","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38612","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41027","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41063","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42107","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42114","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42244","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42246","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-44958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47693","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47703","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49935","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50028","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50045","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50046","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50185","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53224","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56611","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56657","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56712","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57981","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57993","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58012","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-58079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21683","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21694","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21732","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21831","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22089","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23143","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23144","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37853","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37867","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37920","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37959","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38162","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38524","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38643","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39705","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39940","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71127","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23401","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23472","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31518","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31551","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31692","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43499","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23138.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-23138","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39967","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23209","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40358","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40361","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68349","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23035","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23230","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68301","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31400","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31516","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31532","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31533","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43262","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46190","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621230-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1191256","tags":["report"]},{"url":"https://bugzilla.suse.com/1191270","tags":["report"]},{"url":"https://bugzilla.suse.com/1194778","tags":["report"]},{"url":"https://bugzilla.suse.com/1207184","tags":["report"]},{"url":"https://bugzilla.suse.com/1217845","tags":["report"]},{"url":"https://bugzilla.suse.com/1222768","tags":["report"]},{"url":"https://bugzilla.suse.com/1243208","tags":["report"]},{"url":"https://bugzilla.suse.com/1252073","tags":["report"]},{"url":"https://bugzilla.suse.com/1253129","tags":["report"]},{"url":"https://bugzilla.suse.com/1254214","tags":["report"]},{"url":"https://bugzilla.suse.com/1254306","tags":["report"]},{"url":"https://bugzilla.suse.com/1254307","tags":["report"]},{"url":"https://bugzilla.suse.com/1255084","tags":["report"]},{"url":"https://bugzilla.suse.com/1255687","tags":["report"]},{"url":"https://bugzilla.suse.com/1256647","tags":["report"]},{"url":"https://bugzilla.suse.com/1257183","tags":["report"]},{"url":"https://bugzilla.suse.com/1257511","tags":["report"]},{"url":"https://bugzilla.suse.com/1257708","tags":["report"]},{"url":"https://bugzilla.suse.com/1257773","tags":["report"]},{"url":"https://bugzilla.suse.com/1257777","tags":["report"]},{"url":"https://bugzilla.suse.com/1258175","tags":["report"]},{"url":"https://bugzilla.suse.com/1258280","tags":["report"]},{"url":"https://bugzilla.suse.com/1258293","tags":["report"]},{"url":"https://bugzilla.suse.com/1258301","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/1258340","tags":["report"]},{"url":"https://bugzilla.suse.com/1258414","tags":["report"]},{"url":"https://bugzilla.suse.com/1258447","tags":["report"]},{"url":"https://bugzilla.suse.com/1258476","tags":["report"]},{"url":"https://bugzilla.suse.com/1258849","tags":["report"]},{"url":"https://bugzilla.suse.com/1259188","tags":["report"]},{"url":"https://bugzilla.suse.com/1259461","tags":["report"]},{"url":"https://bugzilla.suse.com/1259484","tags":["report"]},{"url":"https://bugzilla.suse.com/1259485","tags":["report"]},{"url":"https://bugzilla.suse.com/1259580","tags":["report"]},{"url":"https://bugzilla.suse.com/1259707","tags":["report"]},{"url":"https://bugzilla.suse.com/1259759","tags":["report"]},{"url":"https://bugzilla.suse.com/1259795","tags":["report"]},{"url":"https://bugzilla.suse.com/1259797","tags":["report"]},{"url":"https://bugzilla.suse.com/1259870","tags":["report"]},{"url":"https://bugzilla.suse.com/1259886","tags":["report"]},{"url":"https://bugzilla.suse.com/1259891","tags":["report"]},{"url":"https://bugzilla.suse.com/1259955","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/1260459","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/1260490","tags":["report"]},{"url":"https://bugzilla.suse.com/1260497","tags":["report"]},{"url":"https://bugzilla.suse.com/1260500","tags":["report"]},{"url":"https://bugzilla.suse.com/1260522","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/1260606","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://bugzilla.suse.com/1261506","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-39998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23138","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-23204","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-23239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23393","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-23419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23425","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-202621237-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621352-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621361-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23138","tags":["report"]},{"url":"https://git.kernel.org/linus/5f1ef0dfcb5b7f4a91a9b0e0ba533efd9f7e2cdb","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8570-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8567-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8594-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8596-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8604-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8605-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8606-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8607-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8608-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8609-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8574-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8595-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8619-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8665-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8669-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-21709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-54518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-62626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23276","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23442","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31417","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31423","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31433","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31434","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31438","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31440","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31446","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31447","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31477","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31498","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31505","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31508","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31509","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31518","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31519","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31522","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31523","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31545","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31554","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31557","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31563","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31565","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31570","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31575","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31580","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31594","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31596","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31597","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31598","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31599","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31611","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31613","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31616","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31617","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31618","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31628","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31638","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31651","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31655","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31656","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31658","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31661","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31674","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31723","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31762","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43370","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43413","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43426","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43432","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43475","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45834","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52958","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71160","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-71180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71182","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-71185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71189","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-71192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71195","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-71198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71201","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-22979","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-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-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-22994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22996","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-23000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23003","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-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-23010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","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-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://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-23025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23026","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-23033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23036","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-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-23047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23050","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-23053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23062","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-23065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23067","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-23070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23072","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-23077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23081","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-23086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23088","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-23092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23094","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-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23102","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-23106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23109","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-23114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23116","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-23122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23123","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-23126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23133","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-23137","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-23143","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-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23158","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-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23170","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-23212","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-53369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63855","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-63865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22984","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-23427","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-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-31635","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-31718","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-43083","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-43125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43376","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-43402","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-45898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46039","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-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","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-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-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-31411","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-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-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-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-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64587","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-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-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-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-23138","title":"tracing: Add recursion protection in kernel stack trace recording","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T15:22:23.385Z","modified":"2026-11-05T21:23:18.84Z","updated_at":"2026-11-05T22:55:19.586268Z"}],"euvd":[{"id":"EUVD-2026-5899","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T15:22:23Z","modified":"2026-11-05T21:23:18Z","updated_at":"2026-11-05T22:02:07.885196Z"}],"ghsa":[{"id":"GHSA-gqpg-53jh-cpqf","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T18:30:14Z","modified":"2026-10-30T15:33:27Z","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:14:46.35353Z"}],"nvd":[{"id":"CVE-2026-23138","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T16:15:53.83Z","modified":"2026-11-05T22:18:03.787Z","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","assessor":"primary"}],"updated_at":"2026-11-05T23:57:16.793383Z"}],"osv":[{"id":"BELL-CVE-2026-23138","status":"published","published":"2026-02-19T06:09:19.573696Z","modified":"2026-11-04T07:15:59.510097666Z","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-04T07:31:49.594962Z"},{"id":"DEBIAN-CVE-2026-23138","description":"In the Linux kernel, the following vulnerability has been resolved:  tracing: Add recursion protection in kernel stack trace recording  A bug was reported about an infinite recursion caused by tracing the rcu events with the kernel stack trace trigger enabled. The stack trace code called back into RCU which then called the stack trace again.  Expand the ftrace recursion protection to add a set of bits to protect events from recursion. Each bit represents the context that the event is in (normal, softirq, interrupt and NMI).  Have the stack trace code use the interrupt context to protect against recursion.  Note, the bug showed an issue in both the RCU code as well as the tracing stacktrace code. This only handles the tracing stack trace side of the bug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T16:15:53.83Z","modified":"2026-11-06T10:04:03.640772782Z","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-06T10:38:22.758306Z"},{"id":"OESA-2026-1569","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\npps: Fix a use-after-free\n\nOn a board running ntpd and gpsd, I\u0026apos;m seeing a consistent use-after-free\nin sys_exit() from gpsd when rebooting:\n\n    pps pps1: removed\n    ------------[ cut here ]------------\n    kobject: \u0026apos;(null)\u0026apos; (00000000db4bec24): is not initialized, yet kobject_put() is being called.\n    WARNING: CPU: 2 PID: 440 at lib/kobject.c:734 kobject_put+0x120/0x150\n    CPU: 2 UID: 299 PID: 440 Comm: gpsd Not tainted 6.11.0-rc6-00308-gb31c44928842 #1\n    Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : kobject_put+0x120/0x150\n    lr : kobject_put+0x120/0x150\n    sp : ffffffc0803d3ae0\n    x29: ffffffc0803d3ae0 x28: ffffff8042dc9738 x27: 0000000000000001\n    x26: 0000000000000000 x25: ffffff8042dc9040 x24: ffffff8042dc9440\n    x23: ffffff80402a4620 x22: ffffff8042ef4bd0 x21: ffffff80405cb600\n    x20: 000000000008001b x19: ffffff8040b3b6e0 x18: 0000000000000000\n    x17: 0000000000000000 x16: 0000000000000000 x15: 696e6920746f6e20\n    x14: 7369203a29343263 x13: 205d303434542020 x12: 0000000000000000\n    x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000\n    x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000\n    x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000\n    x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000\n    Call trace:\n     kobject_put+0x120/0x150\n     cdev_put+0x20/0x3c\n     __fput+0x2c4/0x2d8\n     ____fput+0x1c/0x38\n     task_work_run+0x70/0xfc\n     do_exit+0x2a0/0x924\n     do_group_exit+0x34/0x90\n     get_signal+0x7fc/0x8c0\n     do_signal+0x128/0x13b4\n     do_notify_resume+0xdc/0x160\n     el0_svc+0xd4/0xf8\n     el0t_64_sync_handler+0x140/0x14c\n     el0t_64_sync+0x190/0x194\n    ---[ end trace 0000000000000000 ]---\n\n...followed by more symptoms of corruption, with similar stacks:\n\n    refcount_t: underflow; use-after-free.\n    kernel BUG at lib/list_debug.c:62!\n    Kernel panic - not syncing: Oops - BUG: Fatal exception\n\nThis happens because pps_device_destruct() frees the pps_device with the\nembedded cdev immediately after calling cdev_del(), but, as the comment\nabove cdev_del() notes, fops for previously opened cdevs are still\ncallable even after cdev_del() returns. I think this bug has always\nbeen there: I can\u0026apos;t explain why it suddenly started happening every time\nI reboot this particular board.\n\nIn commit d953e0e837e6 (\u0026quot;pps: Fix a use-after free bug when\nunregistering a source.\u0026quot;), George Spelvin suggested removing the\nembedded cdev. That seems like the simplest way to fix this, so I\u0026apos;ve\nimplemented his suggestion, using __register_chrdev() with pps_idr\nbecoming the source of truth for which minor corresponds to which\ndevice.\n\nBut now that pps_idr defines userspace visibility instead of cdev_add(),\nwe need to be sure the pps-\u0026gt;dev refcount can\u0026apos;t reach zero while\nuserspace can still find it again. So, the idr_remove() call moves to\npps_unregister_cdev(), and pps_idr now holds a reference to pps-\u0026gt;dev.\n\n    pps_core: source serial1 got cdev (251:1)\n    \u0026lt;...\u0026gt;\n    pps pps1: removed\n    pps_core: unregistering pps1\n    pps_core: deallocating pps1(CVE-2024-57979)\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\nfbcon: fix integer overflow in fbcon_do_set_font\n\nFix integer overflow vulnerabilities in fbcon_do_set_font() where font\nsize calculations could overflow when handling user-controlled font\nparameters.\n\nThe vulnerabilities occur when:\n1. CALC_FONTSZ(h, pitch, charcount) performs h * pith * charcount\n   multiplication with user-controlled values that can overflow.\n2. FONT_EXTRA_WORDS * sizeof(int) + size addition can also overflow\n3. This results in smaller allocations than expected, leading to buffer\n   overflows during font data copying.\n\nAdd explicit overflow checking using check_mul_overflow() and\ncheck_add_overflow() kernel helpers to safety validate all size\ncalculations before allocation.(CVE-2025-39967)\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\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, a race condition vulnerability exists in the PCM trigger callback of ALSA driver. The driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are performed outside the cable lock, this may result in UAF (Use-After-Free) when a program attempts to trigger frequently while opening/closing the tied stream.(CVE-2026-23191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: fix error recovery in macvlan_common_newlink()\n\nvalis provided a nice repro to crash the kernel:\n\nip link add p1 type veth peer p2\nip link set address 00:00:00:00:00:20 dev p1\nip link set up dev p1\nip link set up dev p2\n\nip link add mv0 link p2 type macvlan mode source\nip link add invalid% link p2 type macvlan mode source macaddr add 00:00:00:00:00:20\n\nping -c1 -I p1 1.2.3.4\n\nHe also gave a very detailed analysis:\n\n\u0026lt;quote valis\u0026gt;\n\nThe issue is triggered when a new macvlan link is created  with\nMACVLAN_MODE_SOURCE mode and MACVLAN_MACADDR_ADD (or\nMACVLAN_MACADDR_SET) parameter, lower device already has a macvlan\nport and register_netdevice() called from macvlan_common_newlink()\nfails (e.g. because of the invalid link name).\n\nIn this case macvlan_hash_add_source is called from\nmacvlan_change_sources() / macvlan_common_newlink():\n\nThis adds a reference to vlan to the port\u0026apos;s vlan_source_hash using\nmacvlan_source_entry.\n\nvlan is a pointer to the priv data of the link that is being created.\n\nWhen register_netdevice() fails, the error is returned from\nmacvlan_newlink() to rtnl_newlink_create():\n\n        if (ops-\u0026gt;newlink)\n                err = ops-\u0026gt;newlink(dev, \u0026amp;params, extack);\n        else\n                err = register_netdevice(dev);\n        if (err \u0026lt; 0) {\n                free_netdev(dev);\n                goto out;\n        }\n\nand free_netdev() is called, causing a kvfree() on the struct\nnet_device that is still referenced in the source entry attached to\nthe lower device\u0026apos;s macvlan port.\n\nNow all packets sent on the macvlan port with a matching source mac\naddress will trigger a use-after-free in macvlan_forward_source().\n\n\u0026lt;/quote valis\u0026gt;\n\nWith all that, my fix is to make sure we call macvlan_flush_sources()\nregardless of @create value whenever \u0026quot;goto destroy_macvlan_port;\u0026quot;\npath is taken.\n\nMany thanks to valis for following up on this issue.(CVE-2026-23209)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.794373716Z","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-1759","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:44.306450654Z","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-1760","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency\n\nUnder high concurrency, A tree-connection object (tcon) is freed on\na disconnect path while another path still holds a reference and later\nexecutes *_put()/write on it.(CVE-2025-68817)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Cap the number of PCR banks\n\ntpm2_get_pcr_allocation() does not cap any upper limit for the number of\nbanks. Cap the limit to eight banks so that out of bounds values coming\nfrom external I/O cause on only limited harm.(CVE-2025-71077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: change all pageblocks migrate type on coalescing\n\nWhen a page is freed it coalesces with a buddy into a higher order page\nwhile possible.  When the buddy page migrate type differs, it is expected\nto be updated to match the one of the page being freed.\n\nHowever, only the first pageblock of the buddy page is updated, while the\nrest of the pageblocks are left unchanged.\n\nThat causes warnings in later expand() and other code paths (like below),\nsince an inconsistency between migration type of the list containing the\npage and the page-owned pageblocks migration types is introduced.\n\n[  308.986589] ------------[ cut here ]------------\n[  308.987227] page type is 0, passed migratetype is 1 (nr=256)\n[  308.987275] WARNING: CPU: 1 PID: 5224 at mm/page_alloc.c:812 expand+0x23c/0x270\n[  308.987293] Modules linked in: algif_hash(E) af_alg(E) nft_fib_inet(E) nft_fib_ipv4(E) nft_fib_ipv6(E) nft_fib(E) nft_reject_inet(E) nf_reject_ipv4(E) nf_reject_ipv6(E) nft_reject(E) nft_ct(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) s390_trng(E) vfio_ccw(E) mdev(E) vfio_iommu_type1(E) vfio(E) sch_fq_codel(E) drm(E) i2c_core(E) drm_panel_orientation_quirks(E) loop(E) nfnetlink(E) vsock_loopback(E) vmw_vsock_virtio_transport_common(E) vsock(E) ctcm(E) fsm(E) diag288_wdt(E) watchdog(E) zfcp(E) scsi_transport_fc(E) ghash_s390(E) prng(E) aes_s390(E) des_generic(E) des_s390(E) libdes(E) sha3_512_s390(E) sha3_256_s390(E) sha_common(E) paes_s390(E) crypto_engine(E) pkey_cca(E) pkey_ep11(E) zcrypt(E) rng_core(E) pkey_pckmo(E) pkey(E) autofs4(E)\n[  308.987439] Unloaded tainted modules: hmac_s390(E):2\n[  308.987650] CPU: 1 UID: 0 PID: 5224 Comm: mempig_verify Kdump: loaded Tainted: G            E       6.18.0-gcc-bpf-debug #431 PREEMPT\n[  308.987657] Tainted: [E]=UNSIGNED_MODULE\n[  308.987661] Hardware name: IBM 3906 M04 704 (z/VM 7.3.0)\n[  308.987666] Krnl PSW : 0404f00180000000 00000349976fa600 (expand+0x240/0x270)\n[  308.987676]            R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3\n[  308.987682] Krnl GPRS: 0000034980000004 0000000000000005 0000000000000030 000003499a0e6d88\n[  308.987688]            0000000000000005 0000034980000005 000002be803ac000 0000023efe6c8300\n[  308.987692]            0000000000000008 0000034998d57290 000002be00000100 0000023e00000008\n[  308.987696]            0000000000000000 0000000000000000 00000349976fa5fc 000002c99b1eb6f0\n[  308.987708] Krnl Code: 00000349976fa5f0: c020008a02f2\tlarl\t%r2,000003499883abd4\n                          00000349976fa5f6: c0e5ffe3f4b5\tbrasl\t%r14,0000034997378f60\n                         #00000349976fa5fc: af000000\t\tmc\t0,0\n                         \u0026gt;00000349976fa600: a7f4ff4c\t\tbrc\t15,00000349976fa498\n                          00000349976fa604: b9040026\t\tlgr\t%r2,%r6\n                          00000349976fa608: c0300088317f\tlarl\t%r3,0000034998800906\n                          00000349976fa60e: c0e5fffdb6e1\tbrasl\t%r14,00000349976b13d0\n                          00000349976fa614: af000000\t\tmc\t0,0\n[  308.987734] Call Trace:\n[  308.987738]  [\u0026lt;00000349976fa600\u0026gt;] expand+0x240/0x270\n[  308.987744] ([\u0026lt;00000349976fa5fc\u0026gt;] expand+0x23c/0x270)\n[  308.987749]  [\u0026lt;00000349976ff95e\u0026gt;] rmqueue_bulk+0x71e/0x940\n[  308.987754]  [\u0026lt;00000349976ffd7e\u0026gt;] __rmqueue_pcplist+0x1fe/0x2a0\n[  308.987759]  [\u0026lt;0000034997700966\u0026gt;] rmqueue.isra.0+0xb46/0xf40\n[  308.987763]  [\u0026lt;0000034997703ec8\u0026gt;] get_page_from_freelist+0x198/0x8d0\n[  308.987768]  [\u0026lt;0000034997706fa8\u0026gt;] __alloc_frozen_pages_noprof+0x198/0x400\n[  308.987774]  [\u0026lt;00000349977536f8\u0026gt;] alloc_pages_mpol+0xb8/0x220\n[  308.987781]  [\u0026lt;0000034997753bf6\u0026gt;] folio_alloc_mpol_noprof+0x26/0xc0\n[  308.987786]  [\u0026lt;0000034997753e4c\u0026gt;] vma_alloc_folio_noprof+0x6c/0xa0\n[  308.987791]  [\u0026lt;0000034997775b22\u0026gt;] vma_alloc_anon_folio_pmd+0x42/0x240\n[  308.987799]  [\u0026lt;000003499777bfea\u0026gt;] __do_huge_pmd_anonymous_page+0x3a/0x210\n[  308.987804]  [\u0026lt;00000349976cb0\n---truncated---(CVE-2025-71134)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: rtl8150: fix memory leak on usb_submit_urb() failure\n\nIn async_set_registers(), when usb_submit_urb() fails, the allocated\n  async_req structure and URB are not freed, causing a memory leak.\n\n  The completion callback async_set_reg_cb() is responsible for freeing\n  these allocations, but it is only called after the URB is successfully\n  submitted and completes (successfully or with error). If submission\n  fails, the callback never runs and the memory is leaked.\n\n  Fix this by freeing both the URB and the request structure in the error\n  path when usb_submit_urb() fails.(CVE-2025-71154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix bsg_done() causing double free\n\nKernel panic observed on system,\n\n[5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000\n[5353358.825194] #PF: supervisor write access in kernel mode\n[5353358.825195] #PF: error_code(0x0002) - not-present page\n[5353358.825196] PGD 100006067 P4D 0\n[5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI\n[5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G        W    L    -------  ---  5.14.0-503.34.1.el9_5.x86_64 #1\n[5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025\n[5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10\n[5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246\n[5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000\n[5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000\n[5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000\n[5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090\n[5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000\n[5353358.825218] FS:  00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000\n[5353358.825219] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0\n[5353358.825221] PKRU: 55555554\n[5353358.825222] Call Trace:\n[5353358.825223]  \u0026lt;TASK\u0026gt;\n[5353358.825224]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825229]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825232]  ? sg_copy_buffer+0xc8/0x110\n[5353358.825236]  ? __die_body.cold+0x8/0xd\n[5353358.825238]  ? page_fault_oops+0x134/0x170\n[5353358.825242]  ? kernelmode_fixup_or_oops+0x84/0x110\n[5353358.825244]  ? exc_page_fault+0xa8/0x150\n[5353358.825247]  ? asm_exc_page_fault+0x22/0x30\n[5353358.825252]  ? memcpy_erms+0x6/0x10\n[5353358.825253]  sg_copy_buffer+0xc8/0x110\n[5353358.825259]  qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx]\n[5353358.825317]  qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx]\n\nMost routines in qla_bsg.c call bsg_done() only for success cases.\nHowever a few invoke it for failure case as well leading to a double\nfree. Validate before calling bsg_done().(CVE-2025-71238)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: avoid kernel-infoleak from struct iw_point\n\nstruct iw_point has a 32bit hole on 64bit arches.\n\nstruct iw_point {\n  void __user   *pointer;       /* Pointer to the data  (in user space) */\n  __u16         length;         /* number of fields or size in bytes */\n  __u16         flags;          /* Optional params */\n};\n\nMake sure to zero the structure to avoid disclosing 32bits of kernel data\nto user space.(CVE-2026-22978)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: provide locking for v4_end_grace\n\nWriting to v4_end_grace can race with server shutdown and result in\nmemory being accessed after it was freed - reclaim_str_hashtbl in\nparticularly.\n\nWe cannot hold nfsd_mutex across the nfsd4_end_grace() call as that is\nheld while client_tracking_op-\u0026gt;init() is called and that can wait for\nan upcall to nfsdcltrack which can write to v4_end_grace, resulting in a\ndeadlock.\n\nnfsd4_end_grace() is also called by the landromat work queue and this\ndoesn\u0026apos;t require locking as server shutdown will stop the work and wait\nfor it before freeing anything that nfsd4_end_grace() might access.\n\nHowever, we must be sure that writing to v4_end_grace doesn\u0026apos;t restart\nthe work item after shutdown has already waited for it.  For this we\nadd a new flag protected with nn-\u0026gt;client_lock.  It is set only while it\nis safe to make client tracking calls, and v4_end_grace only schedules\nwork while the flag is set with the spinlock held.\n\nSo this patch adds a nfsd_net field \u0026quot;client_tracking_active\u0026quot; which is\nset as described.  Another field \u0026quot;grace_end_forced\u0026quot;, is set when\nv4_end_grace is written.  After this is set, and providing\nclient_tracking_active is set, the laundromat is scheduled.\nThis \u0026quot;grace_end_forced\u0026quot; field bypasses other checks for whether the\ngrace period has finished.\n\nThis resolves a race which can result in use-after-free.(CVE-2026-22980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()\n\nIf the osdmap is (maliciously) corrupted such that the incremental\nosdmap epoch is different from what is expected, there is no need to\nBUG.  Instead, just declare the incremental osdmap to be invalid.(CVE-2026-22990)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: return the handler error from mon_handle_auth_done()\n\nCurrently any error from ceph_auth_handle_reply_done() is propagated\nvia finish_auth() but isn\u0026apos;t returned from mon_handle_auth_done().  This\nresults in higher layers learning that (despite the monitor considering\nus to be successfully authenticated) something went wrong in the\nauthentication phase and reacting accordingly, but msgr2 still trying\nto proceed with establishing the session in the background.  In the\ncase of secure mode this can trigger a WARN in setup_crypto() and later\nlead to a NULL pointer dereference inside of prepare_auth_signature().(CVE-2026-22992)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec\n\nauthencesn assumes an ESP/ESN-formatted AAD. When assoclen is shorter than\nthe minimum expected length, crypto_authenc_esn_decrypt() can advance past\nthe end of the destination scatterlist and trigger a NULL pointer dereference\nin scatterwalk_map_and_copy(), leading to a kernel panic (DoS).\n\nAdd a minimum AAD length check to fail fast on invalid inputs.(CVE-2026-23060)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix potential underflow in virtio_transport_get_credit()\n\nThe credit calculation in virtio_transport_get_credit() uses unsigned\narithmetic:\n\n  ret = vvs-\u0026gt;peer_buf_alloc - (vvs-\u0026gt;tx_cnt - vvs-\u0026gt;peer_fwd_cnt);\n\nIf the peer shrinks its advertised buffer (peer_buf_alloc) while bytes\nare in flight, the subtraction can underflow and produce a large\npositive value, potentially allowing more data to be queued than the\npeer can handle.\n\nReuse virtio_transport_has_space() which already handles this case and\nadd a comment to make it clear why we are doing that.\n\n[Stefano: use virtio_transport_has_space() instead of duplicating the code]\n[Stefano: tweak the commit message](CVE-2026-23069)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: Fix race condition in hwspinlock irqsave routine\n\nPreviously, the address of the shared member \u0026apos;\u0026amp;map-\u0026gt;spinlock_flags\u0026apos; was\npassed directly to \u0026apos;hwspin_lock_timeout_irqsave\u0026apos;. This creates a race\ncondition where multiple contexts contending for the lock could overwrite\nthe shared flags variable, potentially corrupting the state for the\ncurrent lock owner.\n\nFix this by using a local stack variable \u0026apos;flags\u0026apos; to store the IRQ state\ntemporarily.(CVE-2026-23071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: cap TX credit to local buffer size\n\nThe virtio transports derives its TX credit directly from peer_buf_alloc,\nwhich is set from the remote endpoint\u0026apos;s SO_VM_SOCKETS_BUFFER_SIZE value.\n\nOn the host side this means that the amount of data we are willing to\nqueue for a connection is scaled by a guest-chosen buffer size, rather\nthan the host\u0026apos;s own vsock configuration. A malicious guest can advertise\na large buffer and read slowly, causing the host to allocate a\ncorrespondingly large amount of sk_buff memory.\nThe same thing would happen in the guest with a malicious host, since\nvirtio transports share the same code base.\n\nIntroduce a small helper, virtio_transport_tx_buf_size(), that\nreturns min(peer_buf_alloc, buf_alloc), and use it wherever we consume\npeer_buf_alloc.\n\nThis ensures the effective TX window is bounded by both the peer\u0026apos;s\nadvertised buffer and our own buf_alloc (already clamped to\nbuffer_max_size via SO_VM_SOCKETS_BUFFER_MAX_SIZE), so a remote peer\ncannot force the other to queue more data than allowed by its own\nvsock settings.\n\nOn an unpatched Ubuntu 22.04 host (~64 GiB RAM), running a PoC with\n32 guest vsock connections advertising 2 GiB each and reading slowly\ndrove Slab/SUnreclaim from ~0.5 GiB to ~57 GiB; the system only\nrecovered after killing the QEMU process. That said, if QEMU memory is\nlimited with cgroups, the maximum memory used will be limited.\n\nWith this patch applied:\n\n  Before:\n    MemFree:        ~61.6 GiB\n    Slab:           ~142 MiB\n    SUnreclaim:     ~117 MiB\n\n  After 32 high-credit connections:\n    MemFree:        ~61.5 GiB\n    Slab:           ~178 MiB\n    SUnreclaim:     ~152 MiB\n\nOnly ~35 MiB increase in Slab/SUnreclaim, no host OOM, and the guest\nremains responsive.\n\nCompatibility with non-virtio transports:\n\n  - VMCI uses the AF_VSOCK buffer knobs to size its queue pairs per\n    socket based on the local vsk-\u0026gt;buffer_* values; the remote side\n    cannot enlarge those queues beyond what the local endpoint\n    configured.\n\n  - Hyper-V\u0026apos;s vsock transport uses fixed-size VMBus ring buffers and\n    an MTU bound; there is no peer-controlled credit field comparable\n    to peer_buf_alloc, and the remote endpoint cannot drive in-flight\n    kernel memory above those ring sizes.\n\n  - The loopback path reuses virtio_transport_common.c, so it\n    naturally follows the same semantics as the virtio transport.\n\nThis change is limited to virtio_transport_common.c and thus affects\nvirtio-vsock, vhost-vsock, and loopback, bringing them in line with the\n\u0026quot;remote window intersected with local policy\u0026quot; behaviour that VMCI and\nHyper-V already effectively have.\n\n[Stefano: small adjustments after changing the previous patch]\n[Stefano: tweak the commit message](CVE-2026-23086)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: limit BOND_MODE_8023AD to Ethernet devices\n\nBOND_MODE_8023AD makes sense for ARPHRD_ETHER only.\n\nsyzbot reported:\n\n BUG: KASAN: global-out-of-bounds in __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n BUG: KASAN: global-out-of-bounds in __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\nRead of size 16 at addr ffffffff8bf94040 by task syz.1.3580/19497\n\nCPU: 1 UID: 0 PID: 19497 Comm: syz.1.3580 Tainted: G             L      syzkaller #0 PREEMPT(full)\nTainted: [L]=SOFTLOCKUP\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120\n  print_address_description mm/kasan/report.c:378 [inline]\n  print_report+0xca/0x240 mm/kasan/report.c:482\n  kasan_report+0x118/0x150 mm/kasan/report.c:595\n check_region_inline mm/kasan/generic.c:-1 [inline]\n  kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200\n  __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105\n  __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n  __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\n  __dev_mc_add net/core/dev_addr_lists.c:868 [inline]\n  dev_mc_add+0xa1/0x120 net/core/dev_addr_lists.c:886\n  bond_enslave+0x2b8b/0x3ac0 drivers/net/bonding/bond_main.c:2180\n  do_set_master+0x533/0x6d0 net/core/rtnetlink.c:2963\n  do_setlink+0xcf0/0x41c0 net/core/rtnetlink.c:3165\n  rtnl_changelink net/core/rtnetlink.c:3776 [inline]\n  __rtnl_newlink net/core/rtnetlink.c:3935 [inline]\n  rtnl_newlink+0x161c/0x1c90 net/core/rtnetlink.c:4072\n  rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6958\n  netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2550\n  netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n  netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1344\n  netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1894\n  sock_sendmsg_nosec net/socket.c:727 [inline]\n  __sock_sendmsg+0x21c/0x270 net/socket.c:742\n  ____sys_sendmsg+0x505/0x820 net/socket.c:2592\n  ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2646\n  __sys_sendmsg+0x164/0x220 net/socket.c:2678\n  do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n  __do_fast_syscall_32+0x1dc/0x560 arch/x86/entry/syscall_32.c:307\n  do_fast_syscall_32+0x34/0x80 arch/x86/entry/syscall_32.c:332\n entry_SYSENTER_compat_after_hwframe+0x84/0x8e\n \u0026lt;/TASK\u0026gt;\n\nThe buggy address belongs to the variable:\n lacpdu_mcast_addr+0x0/0x40(CVE-2026-23099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvlan: Make the addrs_lock be per port\n\nMake the addrs_lock be per port, not per ipvlan dev.\n\nInitial code seems to be written in the assumption,\nthat any address change must occur under RTNL.\nBut it is not so for the case of IPv6. So\n\n1) Introduce per-port addrs_lock.\n\n2) It was needed to fix places where it was forgotten\nto take lock (ipvlan_open/ipvlan_close)\n\nThis appears to be a very minor problem though.\nSince it\u0026apos;s highly unlikely that ipvlan_add_addr() will\nbe called on 2 CPU simultaneously. But nevertheless,\nthis could cause:\n\n1) False-negative of ipvlan_addr_busy(): one interface\niterated through all port-\u0026gt;ipvlans + ipvlan-\u0026gt;addrs\nunder some ipvlan spinlock, and another added IP\nunder its own lock. Though this is only possible\nfor IPv6, since looks like only ipvlan_addr6_event() can be\ncalled without rtnl_lock.\n\n2) Race since ipvlan_ht_addr_add(port) is called under\ndifferent ipvlan-\u0026gt;addrs_lock locks\n\nThis should not affect performance, since add/remove IP\nis a rare situation and spinlock is not taken on fast\npaths.(CVE-2026-23103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag\n\nThis is more of a preventive patch to make the code more consistent and\nto prevent possible exploits that employ child qlen manipulations on qfq.\nuse cl_is_active instead of relying on the child qdisc\u0026apos;s qlen to determine\nclass activation.(CVE-2026-23105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()\n\nnft_map_catchall_activate() has an inverted element activity check\ncompared to its non-catchall counterpart nft_mapelem_activate() and\ncompared to what is logically required.\n\nnft_map_catchall_activate() is called from the abort path to re-activate\ncatchall map elements that were deactivated during a failed transaction.\nIt should skip elements that are already active (they don\u0026apos;t need\nre-activation) and process elements that are inactive (they need to be\nrestored). Instead, the current code does the opposite: it skips inactive\nelements and processes active ones.\n\nCompare the non-catchall activate callback, which is correct:\n\n  nft_mapelem_activate():\n    if (nft_set_elem_active(ext, iter-\u0026gt;genmask))\n        return 0;   /* skip active, process inactive */\n\nWith the buggy catchall version:\n\n  nft_map_catchall_activate():\n    if (!nft_set_elem_active(ext, genmask))\n        continue;   /* skip inactive, process active */\n\nThe consequence is that when a DELSET operation is aborted,\nnft_setelem_data_activate() is never called for the catchall element.\nFor NFT_GOTO verdict elements, this means nft_data_hold() is never\ncalled to restore the chain-\u0026gt;use reference count. Each abort cycle\npermanently decrements chain-\u0026gt;use. Once chain-\u0026gt;use reaches zero,\nDELCHAIN succeeds and frees the chain while catchall verdict elements\nstill reference it, resulting in a use-after-free.\n\nThis is exploitable for local privilege escalation from an unprivileged\nuser via user namespaces + nftables on distributions that enable\nCONFIG_USER_NS and CONFIG_NF_TABLES.\n\nFix by removing the negation so the check matches nft_mapelem_activate():\nskip active elements, process inactive ones.(CVE-2026-23111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nl2tp: avoid one data-race in l2tp_tunnel_del_work()\n\nWe should read sk-\u0026gt;sk_socket only when dealing with kernel sockets.\n\nsyzbot reported the following data-race:\n\nBUG: KCSAN: data-race in l2tp_tunnel_del_work / sk_common_release\n\nwrite to 0xffff88811c182b20 of 8 bytes by task 5365 on cpu 0:\n  sk_set_socket include/net/sock.h:2092 [inline]\n  sock_orphan include/net/sock.h:2118 [inline]\n  sk_common_release+0xae/0x230 net/core/sock.c:4003\n  udp_lib_close+0x15/0x20 include/net/udp.h:325\n  inet_release+0xce/0xf0 net/ipv4/af_inet.c:437\n  __sock_release net/socket.c:662 [inline]\n  sock_close+0x6b/0x150 net/socket.c:1455\n  __fput+0x29b/0x650 fs/file_table.c:468\n  ____fput+0x1c/0x30 fs/file_table.c:496\n  task_work_run+0x131/0x1a0 kernel/task_work.c:233\n  resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n  __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]\n  exit_to_user_mode_loop+0x1fe/0x740 kernel/entry/common.c:75\n  __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]\n  syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]\n  syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]\n  syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]\n  do_syscall_64+0x1e1/0x2b0 arch/x86/entry/syscall_64.c:100\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff88811c182b20 of 8 bytes by task 827 on cpu 1:\n  l2tp_tunnel_del_work+0x2f/0x1a0 net/l2tp/l2tp_core.c:1418\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340\n  worker_thread+0x582/0x770 kernel/workqueue.c:3421\n  kthread+0x489/0x510 kernel/kthread.c:463\n  ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246\n\nvalue changed: 0xffff88811b818000 -\u0026gt; 0x0000000000000000(CVE-2026-23120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: annotate data-race in ndisc_router_discovery()\n\nsyzbot found that ndisc_router_discovery() could read and write\nin6_dev-\u0026gt;ra_mtu without holding a lock [1]\n\nThis looks fine, IFLA_INET6_RA_MTU is best effort.\n\nAdd READ_ONCE()/WRITE_ONCE() to document the race.\n\nNote that we might also reject illegal MTU values\n(mtu \u0026lt; IPV6_MIN_MTU || mtu \u0026gt; skb-\u0026gt;dev-\u0026gt;mtu) in a future patch.\n\n[1]\nBUG: KCSAN: data-race in ndisc_router_discovery / ndisc_router_discovery\n\nread to 0xffff888119809c20 of 4 bytes by task 25817 on cpu 1:\n  ndisc_router_discovery+0x151d/0x1c90 net/ipv6/ndisc.c:1558\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nwrite to 0xffff888119809c20 of 4 bytes by task 25816 on cpu 0:\n  ndisc_router_discovery+0x155a/0x1c90 net/ipv6/ndisc.c:1559\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nvalue changed: 0x00000000 -\u0026gt; 0xe5400659(CVE-2026-23124)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetdevsim: fix a race issue related to the operation on bpf_bound_progs list\n\nThe netdevsim driver lacks a protection mechanism for operations on the\nbpf_bound_progs list. When the nsim_bpf_create_prog() performs\nlist_add_tail, it is possible that nsim_bpf_destroy_prog() is\nsimultaneously performs list_del. Concurrent operations on the list may\nlead to list corruption and trigger a kernel crash as follows:\n\n[  417.290971] kernel BUG at lib/list_debug.c:62!\n[  417.290983] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n[  417.290992] CPU: 10 PID: 168 Comm: kworker/10:1 Kdump: loaded Not tainted 6.19.0-rc5 #1\n[  417.291003] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  417.291007] Workqueue: events bpf_prog_free_deferred\n[  417.291021] RIP: 0010:__list_del_entry_valid_or_report+0xa7/0xc0\n[  417.291034] Code: a8 ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 48 a1 eb ae e8 ed fb a8 ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 80 a1 eb ae e8 d9 fb a8 ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 d0 a1 eb ae 48 89 f2 48 89 c6 e8 c2 fb a8\n[  417.291040] RSP: 0018:ffffb16a40807df8 EFLAGS: 00010246\n[  417.291046] RAX: 000000000000006d RBX: ffff8e589866f500 RCX: 0000000000000000\n[  417.291051] RDX: 0000000000000000 RSI: ffff8e59f7b23180 RDI: ffff8e59f7b23180\n[  417.291055] RBP: ffffb16a412c9000 R08: 0000000000000000 R09: 0000000000000003\n[  417.291059] R10: ffffb16a40807c80 R11: ffffffffaf9edce8 R12: ffff8e594427ac20\n[  417.291063] R13: ffff8e59f7b44780 R14: ffff8e58800b7a05 R15: 0000000000000000\n[  417.291074] FS:  0000000000000000(0000) GS:ffff8e59f7b00000(0000) knlGS:0000000000000000\n[  417.291079] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  417.291083] CR2: 00007fc4083efe08 CR3: 00000001c3626006 CR4: 0000000000770ee0\n[  417.291088] PKRU: 55555554\n[  417.291091] Call Trace:\n[  417.291096]  \u0026lt;TASK\u0026gt;\n[  417.291103]  nsim_bpf_destroy_prog+0x31/0x80 [netdevsim]\n[  417.291154]  __bpf_prog_offload_destroy+0x2a/0x80\n[  417.291163]  bpf_prog_dev_bound_destroy+0x6f/0xb0\n[  417.291171]  bpf_prog_free_deferred+0x18e/0x1a0\n[  417.291178]  process_one_work+0x18a/0x3a0\n[  417.291188]  worker_thread+0x27b/0x3a0\n[  417.291197]  ? __pfx_worker_thread+0x10/0x10\n[  417.291207]  kthread+0xe5/0x120\n[  417.291214]  ? __pfx_kthread+0x10/0x10\n[  417.291221]  ret_from_fork+0x31/0x50\n[  417.291230]  ? __pfx_kthread+0x10/0x10\n[  417.291236]  ret_from_fork_asm+0x1a/0x30\n[  417.291246]  \u0026lt;/TASK\u0026gt;\n\nAdd a mutex lock, to prevent simultaneous addition and deletion operations\non the list.(CVE-2026-23126)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath10k: fix dma_free_coherent() pointer\n\ndma_alloc_coherent() allocates a DMA mapped buffer and stores the\naddresses in XXX_unaligned fields.  Those should be reused when freeing\nthe buffer rather than the aligned addresses.(CVE-2026-23133)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: reset sparse-read state in osd_fault()\n\nWhen a fault occurs, the connection is abandoned, reestablished, and any\npending operations are retried. The OSD client tracks the progress of a\nsparse-read reply using a separate state machine, largely independent of\nthe messenger\u0026apos;s state.\n\nIf a connection is lost mid-payload or the sparse-read state machine\nreturns an error, the sparse-read state is not reset. The OSD client\nwill then interpret the beginning of a new reply as the continuation of\nthe old one. If this makes the sparse-read machinery enter a failure\nstate, it may never recover, producing loops like:\n\n  libceph:  [0] got 0 extents\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n\nTherefore, reset the sparse-read state in osd_fault(), ensuring retries\nstart from a clean state.(CVE-2026-23136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nof: unittest: Fix memory leak in unittest_data_add()\n\nIn unittest_data_add(), if of_resolve_phandles() fails, the allocated\nunittest_data is not freed, leading to a memory leak.\n\nFix this by using scope-based cleanup helper __free(kfree) for automatic\nresource cleanup. This ensures unittest_data is automatically freed when\nit goes out of scope in error paths.\n\nFor the success path, use retain_and_null_ptr() to transfer ownership\nof the memory to the device tree and prevent double freeing.(CVE-2026-23137)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: update last_gc only when GC has been performed\n\nCurrently last_gc is being updated everytime a new connection is\ntracked, that means that it is updated even if a GC wasn\u0026apos;t performed.\nWith a sufficiently high packet rate, it is possible to always bypass\nthe GC, causing the list to grow infinitely.\n\nUpdate the last_gc value only when a GC has been actually performed.(CVE-2026-23139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix iloc.bh leak in ext4_xattr_inode_update_ref\n\nThe error branch for ext4_xattr_inode_update_ref forget to release the\nrefcount for iloc.bh. Find this when review code.(CVE-2026-23145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix segmentation of forwarding fraglist GRO\n\nThis patch enhances GSO segment handling by properly checking\nthe SKB_GSO_DODGY flag for frag_list GSO packets, addressing\nlow throughput issues observed when a station accesses IPv4\nservers via hotspots with an IPv6-only upstream interface.\n\nSpecifically, it fixes a bug in GSO segmentation when forwarding\nGRO packets containing a frag_list. The function skb_segment_list\ncannot correctly process GRO skbs that have been converted by XLAT,\nsince XLAT only translates the header of the head skb. Consequently,\nskbs in the frag_list may remain untranslated, resulting in protocol\ninconsistencies and reduced throughput.\n\nTo address this, the patch explicitly sets the SKB_GSO_DODGY flag\nfor GSO packets in XLAT\u0026apos;s IPv4/IPv6 protocol translation helpers\n(bpf_skb_proto_4_to_6 and bpf_skb_proto_6_to_4). This marks GSO\npackets as potentially modified after protocol translation. As a\nresult, GSO segmentation will avoid using skb_segment_list and\ninstead falls back to skb_segment for packets with the SKB_GSO_DODGY\nflag. This ensures that only safe and fully translated frag_list\npackets are processed by skb_segment_list, resolving protocol\ninconsistencies and improving throughput when forwarding GRO packets\nconverted by XLAT.(CVE-2026-23154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nefivarfs: fix error propagation in efivar_entry_get()\n\nefivar_entry_get() always returns success even if the underlying\n__efivar_entry_get() fails, masking errors.\n\nThis may result in uninitialized heap memory being copied to userspace\nin the efivarfs_file_read() path.\n\nFix it by returning the error from __efivar_entry_get().(CVE-2026-23156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix race in mptcp_pm_nl_flush_addrs_doit()\n\nsyzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id()\nand/or mptcp_pm_nl_is_backup()\n\nRoot cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit()\nwhich is not RCU ready.\n\nlist_splice_init_rcu() can not be called here while holding pernet-\u0026gt;lock\nspinlock.\n\nMany thanks to Eulgyu Kim for providing a repro and testing our patches.(CVE-2026-23169)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: TC, delete flows only for existing peers\n\nWhen deleting TC steering flows, iterate only over actual devcom\npeers instead of assuming all possible ports exist. This avoids\ntouching non-existent peers and ensures cleanup is limited to\ndevices the driver is currently connected to.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000008\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 133c8a067 P4D 0\n Oops: Oops: 0002 [#1] SMP\n CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core]\n Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff \u0026lt;48\u0026gt; 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49\n RSP: 0018:ff11000143867528 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000\n RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0\n RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002\n R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78\n R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0\n FS:  00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mlx5e_tc_del_flow+0x46/0x270 [mlx5_core]\n  mlx5e_flow_put+0x25/0x50 [mlx5_core]\n  mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core]\n  tc_setup_cb_reoffload+0x20/0x80\n  fl_reoffload+0x26f/0x2f0 [cls_flower]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  tcf_block_playback_offloads+0x9e/0x1c0\n  tcf_block_unbind+0x7b/0xd0\n  tcf_block_setup+0x186/0x1d0\n  tcf_block_offload_cmd.isra.0+0xef/0x130\n  tcf_block_offload_unbind+0x43/0x70\n  __tcf_block_put+0x85/0x160\n  ingress_destroy+0x32/0x110 [sch_ingress]\n  __qdisc_destroy+0x44/0x100\n  qdisc_graft+0x22b/0x610\n  tc_get_qdisc+0x183/0x4d0\n  rtnetlink_rcv_msg+0x2d7/0x3d0\n  ? rtnl_calcit.isra.0+0x100/0x100\n  netlink_rcv_skb+0x53/0x100\n  netlink_unicast+0x249/0x320\n  ? __alloc_skb+0x102/0x1f0\n  netlink_sendmsg+0x1e3/0x420\n  __sock_sendmsg+0x38/0x60\n  ____sys_sendmsg+0x1ef/0x230\n  ? copy_msghdr_from_user+0x6c/0xa0\n  ___sys_sendmsg+0x7f/0xc0\n  ? ___sys_recvmsg+0x8a/0xc0\n  ? __sys_sendto+0x119/0x180\n  __sys_sendmsg+0x61/0xb0\n  do_syscall_64+0x55/0x640\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f35238bb764\n Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55\n RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e\n RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764\n RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003\n RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20\n R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790\n R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780(CVE-2026-23173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: aloop: Fix racy access at PCM trigger\n\nThe PCM trigger callback of aloop driver tries to check the PCM state\nand stop the stream of the tied substream in the corresponding cable.\nSince both check and stop operations are performed outside the cable\nlock, this may result in UAF when a program attempts to trigger\nfrequently while opening/closing the tied stream, as spotted by\nfuzzers.\n\nFor addressing the UAF, this patch changes two things:\n- It covers the most of code in loopback_check_format() with\n  cable-\u0026gt;lock spinlock, and add the proper NULL checks.  This avoids\n  already some racy accesses.\n- In addition, now we try to check the state of the capture PCM stream\n  that may be stopped in this function, which was the major pain point\n  leading to UAF.(CVE-2026-23191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Don\u0026apos;t clobber irqfd routing type when deassigning irqfd\n\nWhen deassigning a KVM_IRQFD, don\u0026apos;t clobber the irqfd\u0026apos;s copy of the IRQ\u0026apos;s\nrouting entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86\nand arm64, which explicitly look for KVM_IRQ_ROUTING_MSI.  Instead, to\nhandle a concurrent routing update, verify that the irqfd is still active\nbefore consuming the routing information.  As evidenced by the x86 and\narm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below),\nclobbering the entry type without notifying arch code is surprising and\nerror prone.\n\nAs a bonus, checking that the irqfd is active provides a convenient\nlocation for documenting _why_ KVM must not consume the routing entry for\nan irqfd that is in the process of being deassigned: once the irqfd is\ndeleted from the list (which happens *before* the eventfd is detached), it\nwill no longer receive updates via kvm_irq_routing_update(), and so KVM\ncould deliver an event using stale routing information (relative to\nKVM_SET_GSI_ROUTING returning to userspace).\n\nAs an even better bonus, explicitly checking for the irqfd being active\nfixes a similar bug to the one the clobbering is trying to prevent: if an\nirqfd is deactivated, and then its routing is changed,\nkvm_irq_routing_update() won\u0026apos;t invoke kvm_arch_update_irqfd_routing()\n(because the irqfd isn\u0026apos;t in the list).  And so if the irqfd is in bypass\nmode, IRQs will continue to be posted using the old routing information.\n\nAs for kvm_arch_irq_bypass_del_producer(), clobbering the routing type\nresults in KVM incorrectly keeping the IRQ in bypass mode, which is\nespecially problematic on AMD as KVM tracks IRQs that are being posted to\na vCPU in a list whose lifetime is tied to the irqfd.\n\nWithout the help of KASAN to detect use-after-free, the most common\nsympton on AMD is a NULL pointer deref in amd_iommu_update_ga() due to\nthe memory for irqfd structure being re-allocated and zeroed, resulting\nin irqfd-\u0026gt;irq_bypass_data being NULL when read by\navic_update_iommu_vcpu_affinity():\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 40cf2b9067 P4D 40cf2b9067 PUD 408362a067 PMD 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 6 UID: 0 PID: 40383 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--5dddc257e6b2-irqfd #31 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:amd_iommu_update_ga+0x19/0xe0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_update_iommu_vcpu_affinity+0x3d/0x90 [kvm_amd]\n   __avic_vcpu_load+0xf4/0x130 [kvm_amd]\n   kvm_arch_vcpu_load+0x89/0x210 [kvm]\n   vcpu_load+0x30/0x40 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x45/0x620 [kvm]\n   kvm_vcpu_ioctl+0x571/0x6a0 [kvm]\n   __se_sys_ioctl+0x6d/0xb0\n   do_syscall_64+0x6f/0x9d0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x46893b\n    \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nIf AVIC is inhibited when the irfd is deassigned, the bug will manifest as\nlist corruption, e.g. on the next irqfd assignment.\n\n  list_add corruption. next-\u0026gt;prev should be prev (ffff8d474d5cd588),\n                       but was 0000000000000000. (next=ffff8d8658f86530).\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:31!\n  Oops: invalid opcode: 0000 [#1] SMP\n  CPU: 128 UID: 0 PID: 80818 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--f19dc4d680ba-irqfd #28 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:__list_add_valid_or_report+0x97/0xc0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_pi_update_irte+0x28e/0x2b0 [kvm_amd]\n   kvm_pi_update_irte+0xbf/0x190 [kvm]\n   kvm_arch_irq_bypass_add_producer+0x72/0x90 [kvm]\n   irq_bypass_register_consumer+0xcd/0x170 [irqbypa\n---truncated---(CVE-2026-23198)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: use skb_header_pointer_careful()\n\nskb_header_pointer() does not fully validate negative @offset values.\n\nUse skb_header_pointer_careful() instead.\n\nGangMin Kim provided a report and a repro fooling u32_classify():\n\nBUG: KASAN: slab-out-of-bounds in u32_classify+0x1180/0x11b0\nnet/sched/cls_u32.c:221(CVE-2026-23204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Prevent excessive number of frames\n\nIn this case, the user constructed the parameters with maxpacksize 40\nfor rate 22050 / pps 1000, and packsize[0] 22 packsize[1] 23. The buffer\nsize for each data URB is maxpacksize * packets, which in this example\nis 40 * 6 = 240; When the user performs a write operation to send audio\ndata into the ALSA PCM playback stream, the calculated number of frames\nis packsize[0] * packets = 264, which exceeds the allocated URB buffer\nsize, triggering the out-of-bounds (OOB) issue reported by syzbot [1].\n\nAdded a check for the number of single data URB frames when calculating\nthe number of frames to prevent [1].\n\n[1]\nBUG: KASAN: slab-out-of-bounds in copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\nWrite of size 264 at addr ffff88804337e800 by task syz.0.17/5506\nCall Trace:\n copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\n prepare_playback_urb+0x953/0x13d0 sound/usb/pcm.c:1611\n prepare_outbound_urb+0x377/0xc50 sound/usb/endpoint.c:333(CVE-2026-23208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: annotate data-races around slave-\u0026gt;last_rx\n\nslave-\u0026gt;last_rx and slave-\u0026gt;target_last_arp_rx[...] can be read and written\nlocklessly. Add READ_ONCE() and WRITE_ONCE() annotations.\n\nsyzbot reported:\n\nBUG: KCSAN: data-race in bond_rcv_validate / bond_rcv_validate\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 1:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n...\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 0:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n  br_netif_receive_skb net/bridge/br_input.c:30 [inline]\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n...\n\nvalue changed: 0x0000000100005365 -\u0026gt; 0x0000000100005366(CVE-2026-23212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbus: fsl-mc: fix use-after-free in driver_override_show()\n\nThe driver_override_show() function reads the driver_override string\nwithout holding the device_lock. However, driver_override_store() uses\ndriver_set_override(), which modifies and frees the string while holding\nthe device_lock.\n\nThis can result in a concurrent use-after-free if the string is freed\nby the store function while being read by the show function.\n\nFix this by holding the device_lock around the read operation.(CVE-2026-23221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: split cached_fid bitfields to avoid shared-byte RMW races\n\nis_open, has_lease and on_list are stored in the same bitfield byte in\nstruct cached_fid but are updated in different code paths that may run\nconcurrently. Bitfield assignments generate byte read–modify–write\noperations (e.g. `orb $mask, addr` on x86_64), so updating one flag can\nrestore stale values of the others.\n\nA possible interleaving is:\n    CPU1: load old byte (has_lease=1, on_list=1)\n    CPU2: clear both flags (store 0)\n    CPU1: RMW store (old | IS_OPEN) -\u0026gt; reintroduces cleared bits\n\nTo avoid this class of races, convert these flags to separate bool\nfields.(CVE-2026-23230)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:55.317925454Z","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-1761","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: atlantic: fix fragment overflow handling in RX path\n\nThe atlantic driver can receive packets with more than MAX_SKB_FRAGS (17)\nfragments when handling large multi-descriptor packets. This causes an\nout-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic.\n\nThe issue occurs because the driver doesn\u0026apos;t check the total number of\nfragments before calling skb_add_rx_frag(). When a packet requires more\nthan MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds.\n\nFix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\nthen all fragments are accounted for. And reusing the existing check to\nprevent the overflow earlier in the code path.\n\nThis crash occurred in production with an Aquantia AQC113 10G NIC.\n\nStack trace from production environment:\n```\nRIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0\nCode: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89\nca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90\nc8 00 00 00 \u0026lt;48\u0026gt; 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48\n89 fa 83\nRSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287\nRAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX:\nfffffffe0a0c8000\nRDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI:\n0000000000037a40\nRBP: 0000000000000024 R08: 0000000000000000 R09:\n0000000000000021\nR10: 0000000000000848 R11: 0000000000000000 R12:\nffffa9bec02a8e24\nR13: ffff925ad8615570 R14: 0000000000000000 R15:\nffff925b22e80a00\nFS: 0000000000000000(0000)\nGS:ffff925e47880000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4:\n0000000000f72ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;IRQ\u0026gt;\naq_ring_rx_clean+0x175/0xe60 [atlantic]\n? aq_ring_rx_clean+0x14d/0xe60 [atlantic]\n? aq_ring_tx_clean+0xdf/0x190 [atlantic]\n? kmem_cache_free+0x348/0x450\n? aq_vec_poll+0x81/0x1d0 [atlantic]\n? __napi_poll+0x28/0x1c0\n? net_rx_action+0x337/0x420\n```\n\nChanges in v4:\n- Add Fixes: tag to satisfy patch validation requirements.\n\nChanges in v3:\n- Fix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\n  then all fragments are accounted for.(CVE-2025-68301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:45.881631165Z","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-2582","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\nmISDN: hfcpci: Fix warning when deleting uninitialized timer\n\nWith CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads\nto the following splat:\n\n[  250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0\n[  250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0\n[  250.218775] Modules linked in: hfcpci(-) mISDN_core\n[  250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)\n[  250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0\n[  250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d\n[  250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286\n[  250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95\n[  250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0\n[  250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39\n[  250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001\n[  250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8\n[  250.232454] FS:  00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:0000000000000000\n[  250.233851] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  250.234856] CR2: 00007f32090a7421 CR3: 0000000004d63000 CR4: 00000000000006f0\n[  250.236117] Call Trace:\n[  250.236599]  \u0026lt;TASK\u0026gt;\n[  250.236967]  ? trace_irq_enable.constprop.0+0xd4/0x130\n[  250.237920]  debug_object_assert_init+0x1f6/0x310\n[  250.238762]  ? __pfx_debug_object_assert_init+0x10/0x10\n[  250.239658]  ? __lock_acquire+0xdea/0x1c70\n[  250.240369]  __try_to_del_timer_sync+0x69/0x140\n[  250.241172]  ? __pfx___try_to_del_timer_sync+0x10/0x10\n[  250.242058]  ? __timer_delete_sync+0xc6/0x120\n[  250.242842]  ? lock_acquire+0x30/0x80\n[  250.243474]  ? __timer_delete_sync+0xc6/0x120\n[  250.244262]  __timer_delete_sync+0x98/0x120\n[  250.245015]  HFC_cleanup+0x10/0x20 [hfcpci]\n[  250.245704]  __do_sys_delete_module+0x348/0x510\n[  250.246461]  ? __pfx___do_sys_delete_module+0x10/0x10\n[  250.247338]  do_syscall_64+0xc1/0x360\n[  250.247924]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix this by initializing hfc_tl timer with DEFINE_TIMER macro.\nAlso, use mod_timer instead of manual timeout update.(CVE-2025-39833)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Add support for Van Gogh SoC\n\nThe ROG Xbox Ally (non-X) SoC features a similar architecture to the\nSteam Deck. While the Steam Deck supports S3 (s2idle causes a crash),\nthis support was dropped by the Xbox Ally which only S0ix suspend.\n\nSince the handler is missing here, this causes the device to not suspend\nand the AMD GPU driver to crash while trying to resume afterwards due to\na power hang.(CVE-2025-68334)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: Move team device type change at the end of team_port_add\n\nAttempting to add a port device that is already up will expectedly fail,\nbut not before modifying the team device header_ops.\n\nIn the case of the syzbot reproducer the gre0 device is\nalready in state UP when it attempts to add it as a\nport device of team0, this fails but before that\nheader_ops-\u0026gt;create of team0 is changed from eth_header to ipgre_header\nin the call to team_dev_type_check_change.\n\nLater when we end up in ipgre_header() struct ip_tunnel* points to nonsense\nas the private data of the device still holds a struct team.\n\nExample sequence of iproute2 commands to reproduce the hang/BUG():\nip link add dev team0 type team\nip link add dev gre0 type gre\nip link set dev gre0 up\nip link set dev gre0 master team0\nip link set dev team0 up\nping -I team0 1.1.1.1\n\nMove team_dev_type_check_change down where all other checks have passed\nas it changes the dev type with no way to restore it in case\none of the checks that follow it fail.\n\nAlso make sure to preserve the origial mtu assignment:\n  - If port_dev is not the same type as dev, dev takes mtu from port_dev\n  - If port_dev is the same type as dev, port_dev takes mtu from dev\n\nThis is done by adding a conditional before the call to dev_set_mtu\nto prevent it from assigning port_dev-\u0026gt;mtu = dev-\u0026gt;mtu and instead\nletting team_dev_type_check_change assign dev-\u0026gt;mtu = port_dev-\u0026gt;mtu.\nThe conditional is needed because the patch moves the call to\nteam_dev_type_check_change past dev_set_mtu.\n\nTesting:\n  - team device driver in-tree selftests\n  - Add/remove various devices as slaves of team device\n  - syzbot(CVE-2025-68340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\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\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n    i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n    i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n  BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n  Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n  CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  Workqueue: iavf iavf_watchdog_task\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x6f/0xb0\n   print_report+0x170/0x4f3\n   kasan_report+0xe1/0x1a0\n   iavf_config_rss+0x619/0x800\n   iavf_watchdog_task+0x2be7/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 63:\n   kasan_save_stack+0x30/0x50\n   kasan_save_track+0x14/0x30\n   __kasan_kmalloc+0x7f/0x90\n   __kmalloc_noprof+0x246/0x6f0\n   iavf_watchdog_task+0x28fc/0x3230\n   process_one_work+0x7fd/0x1420\n   worker_thread+0x4d1/0xd40\n   kthread+0x344/0x660\n   ret_from_fork+0x249/0x320\n   ret_from_fork_asm+0x1a/0x30\n\n  The buggy address belongs to the object at ffff888102c50100\n   which belongs to the cache kmalloc-64 of size 64\n  The buggy address is located 0 bytes to the right of\n   allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n  The buggy address belongs to the physical page:\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n  flags: 0x200000000000000(node=0|zone=2)\n  page_type: f5(slab)\n  raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n  page dumped because: kasan: bad access detected\n\n  Memory state around the buggy address:\n   ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n   ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n  \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n                                       ^\n   ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n   ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb-\u0026gt;vma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb-\u0026gt;vma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb-\u0026gt;vma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer\u0026apos;s vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb-\u0026gt;vma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u0026gt;vma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn\u0026apos;t matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)(CVE-2025-71130)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix deadlock in wait_current_trans() due to ignored transaction type\n\nWhen wait_current_trans() is called during start_transaction(), it\ncurrently waits for a blocked transaction without considering whether\nthe given transaction type actually needs to wait for that particular\ntransaction state. The btrfs_blocked_trans_types[] array already defines\nwhich transaction types should wait for which transaction states, but\nthis check was missing in wait_current_trans().\n\nThis can lead to a deadlock scenario involving two transactions and\npending ordered extents:\n\n  1. Transaction A is in TRANS_STATE_COMMIT_DOING state\n\n  2. A worker processing an ordered extent calls start_transaction()\n     with TRANS_JOIN\n\n  3. join_transaction() returns -EBUSY because Transaction A is in\n     TRANS_STATE_COMMIT_DOING\n\n  4. Transaction A moves to TRANS_STATE_UNBLOCKED and completes\n\n  5. A new Transaction B is created (TRANS_STATE_RUNNING)\n\n  6. The ordered extent from step 2 is added to Transaction B\u0026apos;s\n     pending ordered extents\n\n  7. Transaction B immediately starts commit by another task and\n     enters TRANS_STATE_COMMIT_START\n\n  8. The worker finally reaches wait_current_trans(), sees Transaction B\n     in TRANS_STATE_COMMIT_START (a blocked state), and waits\n     unconditionally\n\n  9. However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START\n     according to btrfs_blocked_trans_types[]\n\n  10. Transaction B is waiting for pending ordered extents to complete\n\n  11. Deadlock: Transaction B waits for ordered extent, ordered extent\n      waits for Transaction B\n\nThis can be illustrated by the following call stacks:\n  CPU0                              CPU1\n                                    btrfs_finish_ordered_io()\n                                      start_transaction(TRANS_JOIN)\n                                        join_transaction()\n                                          # -EBUSY (Transaction A is\n                                          # TRANS_STATE_COMMIT_DOING)\n  # Transaction A completes\n  # Transaction B created\n  # ordered extent added to\n  # Transaction B\u0026apos;s pending list\n  btrfs_commit_transaction()\n    # Transaction B enters\n    # TRANS_STATE_COMMIT_START\n    # waiting for pending ordered\n    # extents\n                                        wait_current_trans()\n                                          # waits for Transaction B\n                                          # (should not wait!)\n\nTask bstore_kv_sync in btrfs_commit_transaction waiting for ordered\nextents:\n\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  btrfs_commit_transaction+0xbf7/0xda0 [btrfs]\n  btrfs_sync_file+0x342/0x4d0 [btrfs]\n  __x64_sys_fdatasync+0x4b/0x80\n  do_syscall_64+0x33/0x40\n  entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nTask kworker in wait_current_trans waiting for transaction commit:\n\n  Workqueue: btrfs-syno_nocow btrfs_work_helper [btrfs]\n  __schedule+0x2e7/0x8a0\n  schedule+0x64/0xe0\n  wait_current_trans+0xb0/0x110 [btrfs]\n  start_transaction+0x346/0x5b0 [btrfs]\n  btrfs_finish_ordered_io.isra.0+0x49b/0x9c0 [btrfs]\n  btrfs_work_helper+0xe8/0x350 [btrfs]\n  process_one_work+0x1d3/0x3c0\n  worker_thread+0x4d/0x3e0\n  kthread+0x12d/0x150\n  ret_from_fork+0x1f/0x30\n\nFix this by passing the transaction type to wait_current_trans() and\nchecking btrfs_blocked_trans_types[cur_trans-\u0026gt;state] against the given\ntype before deciding to wait. This ensures that transaction types which\nare allowed to join during certain blocked states will not unnecessarily\nwait and cause deadlocks.(CVE-2025-71194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: fix possible UAF in macvlan_forward_source()\n\nAdd RCU protection on (struct macvlan_source_entry)-\u0026gt;vlan.\n\nWhenever macvlan_hash_del_source() is called, we must clear\nentry-\u0026gt;vlan pointer before RCU grace period starts.\n\nThis allows macvlan_forward_source() to skip over\nentries queued for freeing.\n\nNote that macvlan_dev are already RCU protected, as they\nare embedded in a standard netdev (netdev_priv(ndev)).\n\nhttps: //lore.kernel.org/netdev/(CVE-2026-23001)\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\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\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\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Enforce that teql can only be used as root qdisc\n\nDesign intent of teql is that it is only supposed to be used as root qdisc.\nWe need to check for that constraint.\n\nAlthough not important, I will describe the scenario that unearthed this\nissue for the curious.\n\nGangMin Kim \u0026lt;(CVE-2026-23074)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: fix hugetlb_pmd_shared()\n\nPatch series \u0026quot;mm/hugetlb: fixes for PMD table sharing (incl.  using\nmmu_gather)\u0026quot;, v3.\n\nOne functional fix, one performance regression fix, and two related\ncomment fixes.\n\nI cleaned up my prototype I recently shared [1] for the performance fix,\ndeferring most of the cleanups I had in the prototype to a later point. \nWhile doing that I identified the other things.\n\nThe goal of this patch set is to be backported to stable trees \u0026quot;fairly\u0026quot;\neasily. At least patch #1 and #4.\n\nPatch #1 fixes hugetlb_pmd_shared() not detecting any sharing\nPatch #2 + #3 are simple comment fixes that patch #4 interacts with.\nPatch #4 is a fix for the reported performance regression due to excessive\nIPI broadcasts during fork()+exit().\n\nThe last patch is all about TLB flushes, IPIs and mmu_gather.\nRead: complicated\n\nThere are plenty of cleanups in the future to be had + one reasonable\noptimization on x86. But that\u0026apos;s all out of scope for this series.\n\nRuntime tested, with a focus on fixing the performance regression using\nthe original reproducer [2] on x86.\n\n\nThis patch (of 4):\n\nWe switched from (wrongly) using the page count to an independent shared\ncount.  Now, shared page tables have a refcount of 1 (excluding\nspeculative references) and instead use ptdesc-\u0026gt;pt_share_count to identify\nsharing.\n\nWe didn\u0026apos;t convert hugetlb_pmd_shared(), so right now, we would never\ndetect a shared PMD table as such, because sharing/unsharing no longer\ntouches the refcount of a PMD table.\n\nPage migration, like mbind() or migrate_pages() would allow for migrating\nfolios mapped into such shared PMD tables, even though the folios are not\nexclusive.  In smaps we would account them as \u0026quot;private\u0026quot; although they are\n\u0026quot;shared\u0026quot;, and we would be wrongly setting the PM_MMAP_EXCLUSIVE in the\npagemap interface.\n\nFix it by properly using ptdesc_pmd_is_shared() in hugetlb_pmd_shared().(CVE-2026-23100)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: secure_seq: add back ports to TS offset\n\nThis reverts 28ee1b746f49 (\u0026quot;secure_seq: downgrade to per-host timestamp offsets\u0026quot;)\n\ntcp_tw_recycle went away in 2017.\n\nZhouyan Deng reported off-path TCP source port leakage via\nSYN cookie side-channel that can be fixed in multiple ways.\n\nOne of them is to bring back TCP ports in TS offset randomization.\n\nAs a bonus, we perform a single siphash() computation\nto provide both an ISN and a TS offset.(CVE-2026-23247)\n\nIn the Linux kernel, a vulnerability exists in the AppArmor module\u0026apos;s unpack_pdb function. The vulnerability occurs due to failure to validate that DFA start states are within bounds, which can lead to out-of-bound reads. An attacker can exploit this vulnerability through specially crafted policy files, potentially leading to information disclosure or system crashes.(CVE-2026-23269)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: unconditionally bump set-\u0026gt;nelems before insertion\n\nIn case that the set is full, a new element gets published then removed\nwithout waiting for the RCU grace period, while RCU reader can be\nwalking over it already.\n\nTo address this issue, add the element transaction even if set is full,\nbut toggle the set_full flag to report -ENFILE so the abort path safely\nunwinds the set to its previous state.\n\nAs for element updates, decrement set-\u0026gt;nelems to restore it.\n\nA simpler fix is to call synchronize_rcu() in the error path.\nHowever, with a large batch adding elements to already maxed-out set,\nthis could cause noticeable slowdown of such batches.(CVE-2026-23272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kaweth: validate USB endpoints\n\nThe kaweth driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it.  If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs\n\nWhen shrinking the number of real tx queues,\nnetif_set_real_num_tx_queues() calls qdisc_reset_all_tx_gt() to flush\nqdiscs for queues which will no longer be used.\n\nqdisc_reset_all_tx_gt() currently serializes qdisc_reset() with\nqdisc_lock(). However, for lockless qdiscs, the dequeue path is\nserialized by qdisc_run_begin/end() using qdisc-\u0026gt;seqlock instead, so\nqdisc_reset() can run concurrently with __qdisc_run() and free skbs\nwhile they are still being dequeued, leading to UAF.\n\nThis can easily be reproduced on e.g. virtio-net by imposing heavy\ntraffic while frequently changing the number of queue pairs:\n\n  iperf3 -ub0 -c $peer -t 0 \u0026amp;\n  while :; do\n    ethtool -L eth0 combined 1\n    ethtool -L eth0 combined 2\n  done\n\nWith KASAN enabled, this leads to reports like:\n\n  BUG: KASAN: slab-use-after-free in __qdisc_run+0x133f/0x1760\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   __qdisc_run+0x133f/0x1760\n   __dev_queue_xmit+0x248f/0x3550\n   ip_finish_output2+0xa42/0x2110\n   ip_output+0x1a7/0x410\n   ip_send_skb+0x2e6/0x480\n   udp_send_skb+0xb0a/0x1590\n   udp_sendmsg+0x13c9/0x1fc0\n   ...\n   \u0026lt;/TASK\u0026gt;\n\n  Allocated by task 1270 on cpu 5 at 44.558414s:\n   ...\n   alloc_skb_with_frags+0x84/0x7c0\n   sock_alloc_send_pskb+0x69a/0x830\n   __ip_append_data+0x1b86/0x48c0\n   ip_make_skb+0x1e8/0x2b0\n   udp_sendmsg+0x13a6/0x1fc0\n   ...\n\n  Freed by task 1306 on cpu 3 at 44.558445s:\n   ...\n   kmem_cache_free+0x117/0x5e0\n   pfifo_fast_reset+0x14d/0x580\n   qdisc_reset+0x9e/0x5f0\n   netif_set_real_num_tx_queues+0x303/0x840\n   virtnet_set_channels+0x1bf/0x260 [virtio_net]\n   ethnl_set_channels+0x684/0xae0\n   ethnl_default_set_doit+0x31a/0x890\n   ...\n\nSerialize qdisc_reset_all_tx_gt() against the lockless dequeue path by\ntaking qdisc-\u0026gt;seqlock for TCQ_F_NOLOCK qdiscs, matching the\nserialization model already used by dev_reset_queue().\n\nAdditionally clear QDISC_STATE_NON_EMPTY after reset so the qdisc state\nreflects an empty queue, avoiding needless re-scheduling.(CVE-2026-23340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_ife: Fix metalist update behavior\n\nWhenever an ife action replace changes the metalist, instead of\nreplacing the old data on the metalist, the current ife code is appending\nthe new metadata. Aside from being innapropriate behavior, this may lead\nto an unbounded addition of metadata to the metalist which might cause an\nout of bounds error when running the encode op:\n\n[  138.423369][    C1] ==================================================================\n[  138.424317][    C1] BUG: KASAN: slab-out-of-bounds in ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.424906][    C1] Write of size 4 at addr ffff8880077f4ffe by task ife_out_out_bou/255\n[  138.425778][    C1] CPU: 1 UID: 0 PID: 255 Comm: ife_out_out_bou Not tainted 7.0.0-rc1-00169-gfbdfa8da05b6 #624 PREEMPT(full)\n[  138.425795][    C1] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n[  138.425800][    C1] Call Trace:\n[  138.425804][    C1]  \u0026lt;IRQ\u0026gt;\n[  138.425808][    C1]  dump_stack_lvl (lib/dump_stack.c:122)\n[  138.425828][    C1]  print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n[  138.425839][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425844][    C1]  ? __virt_addr_valid (./arch/x86/include/asm/preempt.h:95 (discriminator 1) ./include/linux/rcupdate.h:975 (discriminator 1) ./include/linux/mmzone.h:2207 (discriminator 1) arch/x86/mm/physaddr.c:54 (discriminator 1))\n[  138.425853][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425859][    C1]  kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:597)\n[  138.425868][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425878][    C1]  kasan_check_range (mm/kasan/generic.c:186 (discriminator 1) mm/kasan/generic.c:200 (discriminator 1))\n[  138.425884][    C1]  __asan_memset (mm/kasan/shadow.c:84 (discriminator 2))\n[  138.425889][    C1]  ife_tlv_meta_encode (net/ife/ife.c:168)\n[  138.425893][    C1]  ? ife_tlv_meta_encode (net/ife/ife.c:171)\n[  138.425898][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425903][    C1]  ife_encode_meta_u16 (net/sched/act_ife.c:57)\n[  138.425910][    C1]  ? __pfx_do_raw_spin_lock (kernel/locking/spinlock_debug.c:114)\n[  138.425916][    C1]  ? __asan_memcpy (mm/kasan/shadow.c:105 (discriminator 3))\n[  138.425921][    C1]  ? __pfx_ife_encode_meta_u16 (net/sched/act_ife.c:45)\n[  138.425927][    C1]  ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[  138.425931][    C1]  tcf_ife_act (net/sched/act_ife.c:847 net/sched/act_ife.c:879)\n\nTo solve this issue, fix the replace behavior by adding the metalist to\nthe ife rcu data structure.(CVE-2026-23378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix memory leak in ice_set_ringparam()\n\nIn ice_set_ringparam, tx_rings and xdp_rings are allocated before\nrx_rings. If the allocation of rx_rings fails, the code jumps to\nthe done label leaking both tx_rings and xdp_rings. Furthermore, if\nthe setup of an individual Rx ring fails during the loop, the code jumps\nto the free_tx label which releases tx_rings but leaks xdp_rings.\n\nFix this by introducing a free_xdp label and updating the error paths to\nensure both xdp_rings and tx_rings are properly freed if rx_rings\nallocation or setup fails.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-23389)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix side-effect bug in match_char() macro usage\n\nThe match_char() macro evaluates its character parameter multiple\ntimes when traversing differential encoding chains. When invoked\nwith *str++, the string pointer advances on each iteration of the\ninner do-while loop, causing the DFA to check different characters\nat each iteration and therefore skip input characters.\nThis results in out-of-bounds reads when the pointer advances past\nthe input buffer boundary.\n\n[   94.984676] ==================================================================\n[   94.985301] BUG: KASAN: slab-out-of-bounds in aa_dfa_match+0x5ae/0x760\n[   94.985655] Read of size 1 at addr ffff888100342000 by task file/976\n\n[   94.986319] CPU: 7 UID: 1000 PID: 976 Comm: file Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[   94.986322] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   94.986329] Call Trace:\n[   94.986341]  \u0026lt;TASK\u0026gt;\n[   94.986347]  dump_stack_lvl+0x5e/0x80\n[   94.986374]  print_report+0xc8/0x270\n[   94.986384]  ? aa_dfa_match+0x5ae/0x760\n[   94.986388]  kasan_report+0x118/0x150\n[   94.986401]  ? aa_dfa_match+0x5ae/0x760\n[   94.986405]  aa_dfa_match+0x5ae/0x760\n[   94.986408]  __aa_path_perm+0x131/0x400\n[   94.986418]  aa_path_perm+0x219/0x2f0\n[   94.986424]  apparmor_file_open+0x345/0x570\n[   94.986431]  security_file_open+0x5c/0x140\n[   94.986442]  do_dentry_open+0x2f6/0x1120\n[   94.986450]  vfs_open+0x38/0x2b0\n[   94.986453]  ? may_open+0x1e2/0x2b0\n[   94.986466]  path_openat+0x231b/0x2b30\n[   94.986469]  ? __x64_sys_openat+0xf8/0x130\n[   94.986477]  do_file_open+0x19d/0x360\n[   94.986487]  do_sys_openat2+0x98/0x100\n[   94.986491]  __x64_sys_openat+0xf8/0x130\n[   94.986499]  do_syscall_64+0x8e/0x660\n[   94.986515]  ? count_memcg_events+0x15f/0x3c0\n[   94.986526]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986540]  ? handle_mm_fault+0x1639/0x1ef0\n[   94.986551]  ? vma_start_read+0xf0/0x320\n[   94.986558]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986561]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986563]  ? fpregs_assert_state_consistent+0x50/0xe0\n[   94.986572]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986574]  ? arch_exit_to_user_mode_prepare+0x9/0xb0\n[   94.986587]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   94.986588]  ? irqentry_exit+0x3c/0x590\n[   94.986595]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   94.986597] RIP: 0033:0x7fda4a79c3ea\n\nFix by extracting the character value before invoking match_char,\nensuring single evaluation per outer loop.(CVE-2026-23406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix missing bounds check on DEFAULT table in verify_dfa()\n\nThe verify_dfa() function only checks DEFAULT_TABLE bounds when the state\nis not differentially encoded.\n\nWhen the verification loop traverses the differential encoding chain,\nit reads k = DEFAULT_TABLE[j] and uses k as an array index without\nvalidation. A malformed DFA with DEFAULT_TABLE[j] \u0026gt;= state_count,\ntherefore, causes both out-of-bounds reads and writes.\n\n[   57.179855] ==================================================================\n[   57.180549] BUG: KASAN: slab-out-of-bounds in verify_dfa+0x59a/0x660\n[   57.180904] Read of size 4 at addr ffff888100eadec4 by task su/993\n\n[   57.181554] CPU: 1 UID: 0 PID: 993 Comm: su Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[   57.181558] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   57.181563] Call Trace:\n[   57.181572]  \u0026lt;TASK\u0026gt;\n[   57.181577]  dump_stack_lvl+0x5e/0x80\n[   57.181596]  print_report+0xc8/0x270\n[   57.181605]  ? verify_dfa+0x59a/0x660\n[   57.181608]  kasan_report+0x118/0x150\n[   57.181620]  ? verify_dfa+0x59a/0x660\n[   57.181623]  verify_dfa+0x59a/0x660\n[   57.181627]  aa_dfa_unpack+0x1610/0x1740\n[   57.181629]  ? __kmalloc_cache_noprof+0x1d0/0x470\n[   57.181640]  unpack_pdb+0x86d/0x46b0\n[   57.181647]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181653]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181656]  ? aa_unpack_nameX+0x1a8/0x300\n[   57.181659]  aa_unpack+0x20b0/0x4c30\n[   57.181662]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181664]  ? stack_depot_save_flags+0x33/0x700\n[   57.181681]  ? kasan_save_track+0x4f/0x80\n[   57.181683]  ? kasan_save_track+0x3e/0x80\n[   57.181686]  ? __kasan_kmalloc+0x93/0xb0\n[   57.181688]  ? __kvmalloc_node_noprof+0x44a/0x780\n[   57.181693]  ? aa_simple_write_to_buffer+0x54/0x130\n[   57.181697]  ? policy_update+0x154/0x330\n[   57.181704]  aa_replace_profiles+0x15a/0x1dd0\n[   57.181707]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181710]  ? __kvmalloc_node_noprof+0x44a/0x780\n[   57.181712]  ? aa_loaddata_alloc+0x77/0x140\n[   57.181715]  ? srso_alias_return_thunk+0x5/0xfbef5\n[   57.181717]  ? _copy_from_user+0x2a/0x70\n[   57.181730]  policy_update+0x17a/0x330\n[   57.181733]  profile_replace+0x153/0x1a0\n[   57.181735]  ? rw_verify_area+0x93/0x2d0\n[   57.181740]  vfs_write+0x235/0xab0\n[   57.181745]  ksys_write+0xb0/0x170\n[   57.181748]  do_syscall_64+0x8e/0x660\n[   57.181762]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[   57.181765] RIP: 0033:0x7f6192792eb2\n\nRemove the MATCH_FLAG_DIFF_ENCODE condition to validate all DEFAULT_TABLE\nentries unconditionally.(CVE-2026-23407)\n\nA race condition vulnerability exists in the AppArmor security module of the Linux kernel, leading to a use-after-free issue. This vulnerability can be triggered when an attacker simultaneously opens rawdata files and removes an associated AppArmor profile. Since rawdata inodes are not refcounted, there is a time window during profile removal where the i_private pointer may reference freed memory, causing the system to access freed memory regions. This can result in program crashes, unexpected value usage, or arbitrary code execution, threatening the confidentiality, integrity, and availability of the system.(CVE-2026-23410)\n\nA vulnerability exists in the AppArmor security module of the Linux kernel when handling the i_private field of the inode structure. AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can and does live beyond that point and it is possible that some of the fs callback functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs. While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private. This vulnerability could allow a local attacker to bypass AppArmor\u0026apos;s access control policies through a specially crafted request, leading to privilege escalation and impacting system confidentiality, integrity, and availability.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: fix NULL deref caused by udp_sock_create6 when CONFIG_IPV6=n\n\nWhen CONFIG_IPV6 is disabled, the udp_sock_create6() function returns 0\n(success) without actually creating a socket. Callers such as\nfou_create() then proceed to dereference the uninitialized socket\npointer, resulting in a NULL pointer dereference.\n\nThe captured NULL deref crash:\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  RIP: 0010:fou_nl_add_doit (net/ipv4/fou_core.c:590 net/ipv4/fou_core.c:764)\n  [...]\n  Call Trace:\n    \u0026lt;TASK\u0026gt;\n    genl_family_rcv_msg_doit.constprop.0 (net/netlink/genetlink.c:1114)\n    genl_rcv_msg (net/netlink/genetlink.c:1194 net/netlink/genetlink.c:1209)\n    [...]\n    netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n    genl_rcv (net/netlink/genetlink.c:1219)\n    netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n    netlink_sendmsg (net/netlink/af_netlink.c:1894)\n    __sock_sendmsg (net/socket.c:727 (discriminator 1) net/socket.c:742 (discriminator 1))\n    __sys_sendto (./include/linux/file.h:62 (discriminator 1) ./include/linux/file.h:83 (discriminator 1) net/socket.c:2183 (discriminator 1))\n    __x64_sys_sendto (net/socket.c:2213 (discriminator 1) net/socket.c:2209 (discriminator 1) net/socket.c:2209 (discriminator 1))\n    do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n    entry_SYSCALL_64_after_hwframe (net/arch/x86/entry/entry_64.S:130)\n\nThis patch makes udp_sock_create6 return -EPFNOSUPPORT instead, so\ncallers correctly take their error paths. There is only one caller of\nthe vulnerable function and only privileged users can trigger it.(CVE-2026-23439)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix race condition during IPSec ESN update\n\nIn IPSec full offload mode, the device reports an ESN (Extended\nSequence Number) wrap event to the driver. The driver validates this\nevent by querying the IPSec ASO and checking that the esn_event_arm\nfield is 0x0, which indicates an event has occurred. After handling\nthe event, the driver must re-arm the context by setting esn_event_arm\nback to 0x1.\n\nA race condition exists in this handling path. After validating the\nevent, the driver calls mlx5_accel_esp_modify_xfrm() to update the\nkernel\u0026apos;s xfrm state. This function temporarily releases and\nre-acquires the xfrm state lock.\n\nSo, need to acknowledge the event first by setting esn_event_arm to\n0x1. This prevents the driver from reprocessing the same ESN update if\nthe hardware sends events for other reason. Since the next ESN update\nonly occurs after nearly 2^31 packets are received, there\u0026apos;s no risk of\nmissing an update, as it will happen long after this handling has\nfinished.\n\nProcessing the event twice causes the ESN high-order bits (esn_msb) to\nbe incremented incorrectly. The driver then programs the hardware with\nthis invalid ESN state, which leads to anti-replay failures and a\ncomplete halt of IPSec traffic.\n\nFix this by re-arming the ESN event immediately after it is validated,\nbefore calling mlx5_accel_esp_modify_xfrm(). This ensures that any\nspurious, duplicate events are correctly ignored, closing the race\nwindow.(CVE-2026-23440)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Prevent concurrent access to IPSec ASO context\n\nThe query or updating IPSec offload object is through Access ASO WQE.\nThe driver uses a single mlx5e_ipsec_aso struct for each PF, which\ncontains a shared DMA-mapped context for all ASO operations.\n\nA race condition exists because the ASO spinlock is released before\nthe hardware has finished processing WQE. If a second operation is\ninitiated immediately after, it overwrites the shared context in the\nDMA area.\n\nWhen the first operation\u0026apos;s completion is processed later, it reads\nthis corrupted context, leading to unexpected behavior and incorrect\nresults.\n\nThis commit fixes the race by introducing a private context within\neach IPSec offload object. The shared ASO context is now copied to\nthis private context while the ASO spinlock is held. Subsequent\nprocessing uses this saved, per-object context, ensuring its integrity\nis maintained.(CVE-2026-23441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure\n\nieee80211_tx_prepare_skb() has three error paths, but only two of them\nfree the skb. The first error path (ieee80211_tx_prepare() returning\nTX_DROP) does not free it, while invoke_tx_handlers() failure and the\nfragmentation check both do.\n\nAdd kfree_skb() to the first error path so all three are consistent,\nand remove the now-redundant frees in callers (ath9k, mt76,\nmac80211_hwsim) to avoid double-free.\n\nDocument the skb ownership guarantee in the function\u0026apos;s kdoc.(CVE-2026-23444)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check\n\ncdc_ncm_rx_verify_ndp16() validates that the NDP header and its DPE\nentries fit within the skb. The first check correctly accounts for\nndpoffset:\n\n  if ((ndpoffset + sizeof(struct usb_cdc_ncm_ndp16)) \u0026gt; skb_in-\u0026gt;len)\n\nbut the second check omits it:\n\n  if ((sizeof(struct usb_cdc_ncm_ndp16) +\n       ret * (sizeof(struct usb_cdc_ncm_dpe16))) \u0026gt; skb_in-\u0026gt;len)\n\nThis validates the DPE array size against the total skb length as if\nthe NDP were at offset 0, rather than at ndpoffset. When the NDP is\nplaced near the end of the NTB (large wNdpIndex), the DPE entries can\nextend past the skb data buffer even though the check passes.\ncdc_ncm_rx_fixup() then reads out-of-bounds memory when iterating\nthe DPE array.\n\nAdd ndpoffset to the nframes bounds check and use struct_size_t() to\nexpress the NDP-plus-DPE-array size more clearly.(CVE-2026-23448)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock()\n\nSyzkaller reported a panic in smc_tcp_syn_recv_sock() [1].\n\nsmc_tcp_syn_recv_sock() is called in the TCP receive path\n(softirq) via icsk_af_ops-\u0026gt;syn_recv_sock on the clcsock (TCP\nlistening socket). It reads sk_user_data to get the smc_sock\npointer. However, when the SMC listen socket is being closed\nconcurrently, smc_close_active() sets clcsock-\u0026gt;sk_user_data\nto NULL under sk_callback_lock, and then the smc_sock itself\ncan be freed via sock_put() in smc_release().\n\nThis leads to two issues:\n\n1) NULL pointer dereference: sk_user_data is NULL when\n   accessed.\n2) Use-after-free: sk_user_data is read as non-NULL, but the\n   smc_sock is freed before its fields (e.g., queued_smc_hs,\n   ori_af_ops) are accessed.\n\nThe race window looks like this (the syzkaller crash [1]\ntriggers via the SYN cookie path: tcp_get_cookie_sock() -\u0026gt;\nsmc_tcp_syn_recv_sock(), but the normal tcp_check_req() path\nhas the same race):\n\n  CPU A (softirq)              CPU B (process ctx)\n\n  tcp_v4_rcv()\n    TCP_NEW_SYN_RECV:\n    sk = req-\u0026gt;rsk_listener\n    sock_hold(sk)\n    /* No lock on listener */\n                               smc_close_active():\n                                 write_lock_bh(cb_lock)\n                                 sk_user_data = NULL\n                                 write_unlock_bh(cb_lock)\n                                 ...\n                                 smc_clcsock_release()\n                                 sock_put(smc-\u0026gt;sk) x2\n                                   -\u0026gt; smc_sock freed!\n    tcp_check_req()\n      smc_tcp_syn_recv_sock():\n        smc = user_data(sk)\n          -\u0026gt; NULL or dangling\n        smc-\u0026gt;queued_smc_hs\n          -\u0026gt; crash!\n\nNote that the clcsock and smc_sock are two independent objects\nwith separate refcounts. TCP stack holds a reference on the\nclcsock, which keeps it alive, but this does NOT prevent the\nsmc_sock from being freed.\n\nFix this by using RCU and refcount_inc_not_zero() to safely\naccess smc_sock. Since smc_tcp_syn_recv_sock() is called in\nthe TCP three-way handshake path, taking read_lock_bh on\nsk_callback_lock is too heavy and would not survive a SYN\nflood attack. Using rcu_read_lock() is much more lightweight.\n\n- Set SOCK_RCU_FREE on the SMC listen socket so that\n  smc_sock freeing is deferred until after the RCU grace\n  period. This guarantees the memory is still valid when\n  accessed inside rcu_read_lock().\n- Use rcu_read_lock() to protect reading sk_user_data.\n- Use refcount_inc_not_zero(\u0026amp;smc-\u0026gt;sk.sk_refcnt) to pin the\n  smc_sock. If the refcount has already reached zero (close\n  path completed), it returns false and we bail out safely.\n\nNote: smc_hs_congested() has a similar lockless read of\nsk_user_data without rcu_read_lock(), but it only checks for\nNULL and accesses the global smc_hs_wq, never dereferencing\nany smc_sock field, so it is not affected.\n\nReproducer was verified with mdelay injection and smc_run,\nthe issue no longer occurs with this patch applied.\n\n[1] https://syzkaller.appspot.com/bug?extid=827ae2bfb3a3529333e9(CVE-2026-23450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM: runtime: Fix a race condition related to device removal\n\nThe following code in pm_runtime_work() may dereference the dev-\u0026gt;parent\npointer after the parent device has been freed:\n\n\t/* Maybe the parent is now able to suspend. */\n\tif (parent \u0026amp;\u0026amp; !parent-\u0026gt;power.ignore_children) {\n\t\tspin_unlock(\u0026amp;dev-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;parent-\u0026gt;power.lock);\n\t\trpm_idle(parent, RPM_ASYNC);\n\t\tspin_unlock(\u0026amp;parent-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;dev-\u0026gt;power.lock);\n\t}\n\nFix this by inserting a flush_work() call in pm_runtime_remove().\n\nWithout this patch blktest block/001 triggers the following complaint\nsporadically:\n\nBUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160\nRead of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081\nWorkqueue: pm pm_runtime_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x61/0x80\n print_address_description.constprop.0+0x8b/0x310\n print_report+0xfd/0x1d7\n kasan_report+0xd8/0x1d0\n __kasan_check_byte+0x42/0x60\n lock_acquire.part.0+0x38/0x230\n lock_acquire+0x70/0x160\n _raw_spin_lock+0x36/0x50\n rpm_suspend+0xc6a/0xfe0\n rpm_idle+0x578/0x770\n pm_runtime_work+0xee/0x120\n process_one_work+0xde3/0x1410\n worker_thread+0x5eb/0xfe0\n kthread+0x37b/0x480\n ret_from_fork+0x6cb/0x920\n ret_from_fork_asm+0x11/0x20\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_alloc_info+0x3d/0x50\n __kasan_kmalloc+0xa0/0xb0\n __kmalloc_noprof+0x311/0x990\n scsi_alloc_target+0x122/0xb60 [scsi_mod]\n __scsi_scan_target+0x101/0x460 [scsi_mod]\n scsi_scan_channel+0x179/0x1c0 [scsi_mod]\n scsi_scan_host_selected+0x259/0x2d0 [scsi_mod]\n store_scan+0x2d2/0x390 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810\n do_syscall_64+0xee/0xfc0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nFreed by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_free_info+0x3f/0x50\n __kasan_slab_free+0x67/0x80\n kfree+0x225/0x6c0\n scsi_target_dev_release+0x3d/0x60 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_dev_release+0xacf/0x12c0 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_put+0x7f/0xc0 [scsi_mod]\n sdev_store_delete+0xa5/0x120 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810(CVE-2026-23452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user\n\nAfter commit ab4eedb790ca (\u0026quot;Bluetooth: L2CAP: Fix corrupted list in\nhci_chan_del\u0026quot;), l2cap_conn_del() uses conn-\u0026gt;lock to protect access to\nconn-\u0026gt;users. However, l2cap_register_user() and l2cap_unregister_user()\ndon\u0026apos;t use conn-\u0026gt;lock, creating a race condition where these functions can\naccess conn-\u0026gt;users and conn-\u0026gt;hchan concurrently with l2cap_conn_del().\n\nThis can lead to use-after-free and list corruption bugs, as reported\nby syzbot.\n\nFix this by changing l2cap_register_user() and l2cap_unregister_user()\nto use conn-\u0026gt;lock instead of hci_dev_lock(), ensuring consistent locking\nfor the l2cap_conn structure.(CVE-2026-23461)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2026-23473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: fix statistics allocation\n\nThe controller per-cpu statistics is not allocated until after the\ncontroller has been registered with driver core, which leaves a window\nwhere accessing the sysfs attributes can trigger a NULL-pointer\ndereference.\n\nFix this by moving the statistics allocation to controller allocation\nwhile tying its lifetime to that of the controller (rather than using\nimplicit devres).(CVE-2026-23475)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix krb5 mount with username option\n\nCustomer reported that some of their krb5 mounts were failing against\na single server as the client was trying to mount the shares with\nwrong credentials.  It turned out the client was reusing SMB session\nfrom first mount to try mounting the other shares, even though a\ndifferent username= option had been specified to the other mounts.\n\nBy using username mount option along with sec=krb5 to search for\nprincipals from keytab is supported by cifs.upcall(8) since\ncifs-utils-4.8.  So fix this by matching username mount option in\nmatch_session() even with Kerberos.\n\nFor example, the second mount below should fail with -ENOKEY as there\nis no \u0026apos;foobar\u0026apos; principal in keytab (/etc/krb5.keytab).  The client\nends up reusing SMB session from first mount to perform the second\none, which is wrong.\n\n```\n$ ktutil\nktutil:  add_entry -password -p testuser -k 1 -e aes256-cts\nPassword for (CVE-2026-31392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/rmap: fix incorrect pte restoration for lazyfree folios\n\nWe batch unmap anonymous lazyfree folios by folio_unmap_pte_batch.  If the\nbatch has a mix of writable and non-writable bits, we may end up setting\nthe entire batch writable.  Fix this by respecting writable bit during\nbatching.\n\nAlthough on a successful unmap of a lazyfree folio, the soft-dirty bit is\nlost, preserve it on pte restoration by respecting the bit during\nbatching, to make the fix consistent w.r.t both writable bit and\nsoft-dirty bit.\n\nI was able to write the below reproducer and crash the kernel. \nExplanation of reproducer (set 64K mTHP to always):\n\nFault in a 64K large folio.  Split the VMA at mid-point with\nMADV_DONTFORK.  fork() - parent points to the folio with 8 writable ptes\nand 8 non-writable ptes.  Merge the VMAs with MADV_DOFORK so that\nfolio_unmap_pte_batch() can determine all the 16 ptes as a batch.  Do\nMADV_FREE on the range to mark the folio as lazyfree.  Write to the memory\nto dirty the pte, eventually rmap will dirty the folio.  Then trigger\nreclaim, we will hit the pte restoration path, and the kernel will crash\nwith the trace given below.\n\nThe BUG happens at:\n\n\tBUG_ON(atomic_inc_return(\u0026amp;ptc-\u0026gt;anon_map_count) \u0026gt; 1 \u0026amp;\u0026amp; rw);\n\nThe code path is asking for anonymous page to be mapped writable into the\npagetable.  The BUG_ON() firing implies that such a writable page has been\nmapped into the pagetables of more than one process, which breaks\nanonymous memory/CoW semantics.\n\n[   21.134473] kernel BUG at mm/page_table_check.c:118!\n[   21.134497] Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP\n[   21.135917] Modules linked in:\n[   21.136085] CPU: 1 UID: 0 PID: 1735 Comm: dup-lazyfree Not tainted 7.0.0-rc1-00116-g018018a17770 #1028 PREEMPT\n[   21.136858] Hardware name: linux,dummy-virt (DT)\n[   21.137019] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[   21.137308] pc : page_table_check_set+0x28c/0x2a8\n[   21.137607] lr : page_table_check_set+0x134/0x2a8\n[   21.137885] sp : ffff80008a3b3340\n[   21.138124] x29: ffff80008a3b3340 x28: fffffdffc3d14400 x27: ffffd1a55e03d000\n[   21.138623] x26: 0040000000000040 x25: ffffd1a55f7dd000 x24: 0000000000000001\n[   21.139045] x23: 0000000000000001 x22: 0000000000000001 x21: ffffd1a55f217f30\n[   21.139629] x20: 0000000000134521 x19: 0000000000134519 x18: 005c43e000040000\n[   21.140027] x17: 0001400000000000 x16: 0001700000000000 x15: 000000000000ffff\n[   21.140578] x14: 000000000000000c x13: 005c006000000000 x12: 0000000000000020\n[   21.140828] x11: 0000000000000000 x10: 005c000000000000 x9 : ffffd1a55c079ee0\n[   21.141077] x8 : 0000000000000001 x7 : 005c03e000040000 x6 : 000000004000ffff\n[   21.141490] x5 : ffff00017fffce00 x4 : 0000000000000001 x3 : 0000000000000002\n[   21.141741] x2 : 0000000000134510 x1 : 0000000000000000 x0 : ffff0000c08228c0\n[   21.141991] Call trace:\n[   21.142093]  page_table_check_set+0x28c/0x2a8 (P)\n[   21.142265]  __page_table_check_ptes_set+0x144/0x1e8\n[   21.142441]  __set_ptes_anysz.constprop.0+0x160/0x1a8\n[   21.142766]  contpte_set_ptes+0xe8/0x140\n[   21.142907]  try_to_unmap_one+0x10c4/0x10d0\n[   21.143177]  rmap_walk_anon+0x100/0x250\n[   21.143315]  try_to_unmap+0xa0/0xc8\n[   21.143441]  shrink_folio_list+0x59c/0x18a8\n[   21.143759]  shrink_lruvec+0x664/0xbf0\n[   21.144043]  shrink_node+0x218/0x878\n[   21.144285]  __node_reclaim.constprop.0+0x98/0x338\n[   21.144763]  user_proactive_reclaim+0x2a4/0x340\n[   21.145056]  reclaim_store+0x3c/0x60\n[   21.145216]  dev_attr_store+0x20/0x40\n[   21.145585]  sysfs_kf_write+0x84/0xa8\n[   21.145835]  kernfs_fop_write_iter+0x130/0x1c8\n[   21.145994]  vfs_write+0x2b8/0x368\n[   21.146119]  ksys_write+0x70/0x110\n[   21.146240]  __arm64_sys_write+0x24/0x38\n[   21.146380]  invoke_syscall+0x50/0x120\n[   21.146513]  el0_svc_common.constprop.0+0x48/0xf8\n[   21.146679]  do_el0_svc+0x28/0x40\n[   21.146798]  el0_svc+0x34/0x110\n[   21.146926]  el0t\n---truncated---(CVE-2026-31398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm/bus: Fix potential use after free in asynchronous initialization\n\nDingisoul with KASAN reports a use after free if device_add() fails in\nnd_async_device_register().\n\nCommit b6eae0f61db2 (\u0026quot;libnvdimm: Hold reference on parent while\nscheduling async init\u0026quot;) correctly added a reference on the parent device\nto be held until asynchronous initialization was complete.  However, if\ndevice_add() results in an allocation failure the ref count of the\ndevice drops to 0 prior to the parent pointer being accessed.  Thus\nresulting in use after free.\n\nThe bug bot AI correctly identified the fix.  Save a reference to the\nparent pointer to be used to drop the parent reference regardless of the\noutcome of device_add().(CVE-2026-31399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: fix cache_request leak in cache_release\n\nWhen a reader\u0026apos;s file descriptor is closed while in the middle of reading\na cache_request (rp-\u0026gt;offset != 0), cache_release() decrements the\nrequest\u0026apos;s readers count but never checks whether it should free the\nrequest.\n\nIn cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the\ncache_request is removed from the queue and freed along with its buffer\nand cache_head reference. cache_release() lacks this cleanup.\n\nThe only other path that frees requests with readers == 0 is\ncache_dequeue(), but it runs only when CACHE_PENDING transitions from\nset to clear. If that transition already happened while readers was\nstill non-zero, cache_dequeue() will have skipped the request, and no\nsubsequent call will clean it up.\n\nAdd the same cleanup logic from cache_read() to cache_release(): after\ndecrementing readers, check if it reached 0 with CACHE_PENDING clear,\nand if so, dequeue and free the cache_request.(CVE-2026-31400)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd\n\nThe /proc/fs/nfs/exports proc entry is created at module init\nand persists for the module\u0026apos;s lifetime. exports_proc_open()\ncaptures the caller\u0026apos;s current network namespace and stores\nits svc_export_cache in seq-\u0026gt;private, but takes no reference\non the namespace. If the namespace is subsequently torn down\n(e.g. container destruction after the opener does setns() to a\ndifferent namespace), nfsd_net_exit() calls nfsd_export_shutdown()\nwhich frees the cache. Subsequent reads on the still-open fd\ndereference the freed cache_detail, walking a freed hash table.\n\nHold a reference on the struct net for the lifetime of the open\nfile descriptor. This prevents nfsd_net_exit() from running --\nand thus prevents nfsd_export_shutdown() from freeing the cache\n-- while any exports fd is open. cache_detail already stores\nits net pointer (cd-\u0026gt;net, set by cache_create_net()), so\nexports_release() can retrieve it without additional per-file\nstorage.(CVE-2026-31403)\n\nIn the Linux kernel, the Bluetooth SCO module\u0026apos;s sco_recv_frame() function contains a use-after-free vulnerability. The function reads conn-\u0026gt;sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() operation can free the socket between the lock release and the subsequent sk-\u0026gt;sk_state access, resulting in a use-after-free vulnerability. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold references under the lock. The vulnerability is fixed by using sco_sock_hold() to acquire a reference before releasing the lock and adding sock_put() on all exit paths.(CVE-2026-31408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_fw: fix NULL pointer dereference on shared blocks\n\nThe old-method path in fw_classify() calls tcf_block_q() and\ndereferences q-\u0026gt;handle.  Shared blocks leave block-\u0026gt;q NULL, causing a\nNULL deref when an empty cls_fw filter is attached to a shared block\nand a packet with a nonzero major skb mark is classified.\n\nReject the configuration in fw_change() when the old method (no\nTCA_OPTIONS) is used on a shared block, since fw_classify()\u0026apos;s\nold-method path needs block-\u0026gt;q which is NULL for shared blocks.\n\nThe fixed null-ptr-deref calling stack:\n KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\n RIP: 0010:fw_classify (net/sched/cls_fw.c:81)\n Call Trace:\n  tcf_classify (./include/net/tc_wrapper.h:197 net/sched/cls_api.c:1764 net/sched/cls_api.c:1860)\n  tc_run (net/core/dev.c:4401)\n  __dev_queue_xmit (net/core/dev.c:4535 net/core/dev.c:4790)(CVE-2026-31421)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_flow: fix NULL pointer dereference on shared blocks\n\nflow_change() calls tcf_block_q() and dereferences q-\u0026gt;handle to derive\na default baseclass.  Shared blocks leave block-\u0026gt;q NULL, causing a NULL\nderef when a flow filter without a fully qualified baseclass is created\non a shared block.\n\nCheck tcf_block_shared() before accessing block-\u0026gt;q and return -EINVAL\nfor shared blocks.  This avoids the null-deref shown below:\n\n=======================================================================\nKASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\nRIP: 0010:flow_change (net/sched/cls_flow.c:508)\nCall Trace:\n tc_new_tfilter (net/sched/cls_api.c:2432)\n rtnetlink_rcv_msg (net/core/rtnetlink.c:6980)\n [...]\n=======================================================================(CVE-2026-31422)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: EC: clean up handlers on probe failure in acpi_ec_setup()\n\nWhen ec_install_handlers() returns -EPROBE_DEFER on reduced-hardware\nplatforms, it has already started the EC and installed the address\nspace handler with the struct acpi_ec pointer as handler context.\nHowever, acpi_ec_setup() propagates the error without any cleanup.\n\nThe caller acpi_ec_add() then frees the struct acpi_ec for non-boot\ninstances, leaving a dangling handler context in ACPICA.\n\nAny subsequent AML evaluation that accesses an EC OpRegion field\ndispatches into acpi_ec_space_handler() with the freed pointer,\ncausing a use-after-free:\n\n BUG: KASAN: slab-use-after-free in mutex_lock (kernel/locking/mutex.c:289)\n Write of size 8 at addr ffff88800721de38 by task init/1\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mutex_lock (kernel/locking/mutex.c:289)\n  acpi_ec_space_handler (drivers/acpi/ec.c:1362)\n  acpi_ev_address_space_dispatch (drivers/acpi/acpica/evregion.c:293)\n  acpi_ex_access_region (drivers/acpi/acpica/exfldio.c:246)\n  acpi_ex_field_datum_io (drivers/acpi/acpica/exfldio.c:509)\n  acpi_ex_extract_from_field (drivers/acpi/acpica/exfldio.c:700)\n  acpi_ex_read_data_from_field (drivers/acpi/acpica/exfield.c:327)\n  acpi_ex_resolve_node_to_value (drivers/acpi/acpica/exresolv.c:392)\n  \u0026lt;/TASK\u0026gt;\n\n Allocated by task 1:\n  acpi_ec_alloc (drivers/acpi/ec.c:1424)\n  acpi_ec_add (drivers/acpi/ec.c:1692)\n\n Freed by task 1:\n  kfree (mm/slub.c:6876)\n  acpi_ec_add (drivers/acpi/ec.c:1751)\n\nThe bug triggers on reduced-hardware EC platforms (ec-\u0026gt;gpe \u0026lt; 0)\nwhen the GPIO IRQ provider defers probing. Once the stale handler\nexists, any unprivileged sysfs read that causes AML to touch an\nEC OpRegion (battery, thermal, backlight) exercises the dangling\npointer.\n\nFix this by calling ec_remove_handlers() in the error path of\nacpi_ec_setup() before clearing first_ec. ec_remove_handlers()\nchecks each EC_FLAGS_* bit before acting, so it is safe to call\nregardless of how far ec_install_handlers() progressed:\n\n  -ENODEV  (handler not installed): only calls acpi_ec_stop()\n  -EPROBE_DEFER (handler installed): removes handler, stops EC(CVE-2026-31426)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skb: fix cross-cache free of KFENCE-allocated skb head\n\nSKB_SMALL_HEAD_CACHE_SIZE is intentionally set to a non-power-of-2\nvalue (e.g. 704 on x86_64) to avoid collisions with generic kmalloc\nbucket sizes. This ensures that skb_kfree_head() can reliably use\nskb_end_offset to distinguish skb heads allocated from\nskb_small_head_cache vs. generic kmalloc caches.\n\nHowever, when KFENCE is enabled, kfence_ksize() returns the exact\nrequested allocation size instead of the slab bucket size. If a caller\n(e.g. bpf_test_init) allocates skb head data via kzalloc() and the\nrequested size happens to equal SKB_SMALL_HEAD_CACHE_SIZE, then\nslab_build_skb() -\u0026gt; ksize() returns that exact value. After subtracting\nskb_shared_info overhead, skb_end_offset ends up matching\nSKB_SMALL_HEAD_HEADROOM, causing skb_kfree_head() to incorrectly free\nthe object to skb_small_head_cache instead of back to the original\nkmalloc cache, resulting in a slab cross-cache free:\n\n  kmem_cache_free(skbuff_small_head): Wrong slab cache. Expected\n  skbuff_small_head but got kmalloc-1k\n\nFix this by always calling kfree(head) in skb_kfree_head(). This keeps\nthe free path generic and avoids allocator-specific misclassification\nfor KFENCE objects.(CVE-2026-31429)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nX.509: Fix out-of-bounds access when parsing extensions\n\nLeo reports an out-of-bounds access when parsing a certificate with\nempty Basic Constraints or Key Usage extension because the first byte of\nthe extension is read before checking its length.  Fix it.\n\nThe bug can be triggered by an unprivileged user by submitting a\nspecially crafted certificate to the kernel through the keyrings(7) API.\nLeo has demonstrated this with a proof-of-concept program responsibly\ndisclosed off-list.(CVE-2026-31430)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix memory leak when a wq is reset\n\nidxd_wq_disable_cleanup() which is called from the reset path for a\nworkqueue, sets the wq type to NONE, which for other parts of the\ndriver mean that the wq is empty (all its resources were released).\n\nOnly set the wq type to NONE after its resources are released.(CVE-2026-31441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix possible invalid memory access after FLR\n\nIn the case that the first Function Level Reset (FLR) concludes\ncorrectly, but in the second FLR the scratch area for the saved\nconfiguration cannot be allocated, it\u0026apos;s possible for a invalid memory\naccess to happen.\n\nAlways set the deallocated scratch area to NULL after FLR completes.(CVE-2026-31442)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix use-after-free in update_super_work when racing with umount\n\nCommit b98535d09179 (\u0026quot;ext4: fix bug_on in start_this_handle during umount\nfilesystem\u0026quot;) moved ext4_unregister_sysfs() before flushing s_sb_upd_work\nto prevent new error work from being queued via /proc/fs/ext4/xx/mb_groups\nreads during unmount. However, this introduced a use-after-free because\nupdate_super_work calls ext4_notify_error_sysfs() -\u0026gt; sysfs_notify() which\naccesses the kobject\u0026apos;s kernfs_node after it has been freed by kobject_del()\nin ext4_unregister_sysfs():\n\n  update_super_work                ext4_put_super\n  -----------------                --------------\n                                   ext4_unregister_sysfs(sb)\n                                     kobject_del(\u0026amp;sbi-\u0026gt;s_kobj)\n                                       __kobject_del()\n                                         sysfs_remove_dir()\n                                           kobj-\u0026gt;sd = NULL\n                                         sysfs_put(sd)\n                                           kernfs_put()  // RCU free\n  ext4_notify_error_sysfs(sbi)\n    sysfs_notify(\u0026amp;sbi-\u0026gt;s_kobj)\n      kn = kobj-\u0026gt;sd              // stale pointer\n      kernfs_get(kn)             // UAF on freed kernfs_node\n                                   ext4_journal_destroy()\n                                     flush_work(\u0026amp;sbi-\u0026gt;s_sb_upd_work)\n\nInstead of reordering the teardown sequence, fix this by making\next4_notify_error_sysfs() detect that sysfs has already been torn down\nby checking s_kobj.state_in_sysfs, and skipping the sysfs_notify() call\nin that case. A dedicated mutex (s_error_notify_mutex) serializes\next4_notify_error_sysfs() against kobject_del() in ext4_unregister_sysfs()\nto prevent TOCTOU races where the kobject could be deleted between the\nstate_in_sysfs check and the sysfs_notify() call.(CVE-2026-31446)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: validate p_idx bounds in ext4_ext_correct_indexes\n\next4_ext_correct_indexes() walks up the extent tree correcting\nindex entries when the first extent in a leaf is modified. Before\naccessing path[k].p_idx-\u0026gt;ei_block, there is no validation that\np_idx falls within the valid range of index entries for that\nlevel.\n\nIf the on-disk extent header contains a corrupted or crafted\neh_entries value, p_idx can point past the end of the allocated\nbuffer, causing a slab-out-of-bounds read.\n\nFix this by validating path[k].p_idx against EXT_LAST_INDEX() at\nboth access sites: before the while loop and inside it. Return\n-EFSCORRUPTED if the index pointer is out of range, consistent\nwith how other bounds violations are handled in the ext4 extent\ntree code.(CVE-2026-31449)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: publish jinode after initialization\n\next4_inode_attach_jinode() publishes ei-\u0026gt;jinode to concurrent users.\nIt used to set ei-\u0026gt;jinode before jbd2_journal_init_jbd_inode(),\nallowing a reader to observe a non-NULL jinode with i_vfs_inode\nstill unset.\n\nThe fast commit flush path can then pass this jinode to\njbd2_wait_inode_data(), which dereferences i_vfs_inode-\u0026gt;i_mapping and\nmay crash.\n\nBelow is the crash I observe:\n```\nBUG: unable to handle page fault for address: 000000010beb47f4\nPGD 110e51067 P4D 110e51067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\nRIP: 0010:xas_find_marked+0x3d/0x2e0\nCode: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f \u0026lt;49\u0026gt; 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02\nRSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246\nRAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003\nRDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10\nRBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec\nR10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000\nR13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88\nFS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;TASK\u0026gt;\nfilemap_get_folios_tag+0x87/0x2a0\n__filemap_fdatawait_range+0x5f/0xd0\n? srso_alias_return_thunk+0x5/0xfbef5\n? __schedule+0x3e7/0x10c0\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? cap_safe_nice+0x37/0x70\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\nfilemap_fdatawait_range_keep_errors+0x12/0x40\next4_fc_commit+0x697/0x8b0\n? ext4_file_write_iter+0x64b/0x950\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? vfs_write+0x356/0x480\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\next4_sync_file+0xf7/0x370\ndo_fsync+0x3b/0x80\n? syscall_trace_enter+0x108/0x1d0\n__x64_sys_fdatasync+0x16/0x20\ndo_syscall_64+0x62/0x2c0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\n...\n```\n\nFix this by initializing the jbd2_inode first.\nUse smp_wmb() and WRITE_ONCE() to publish ei-\u0026gt;jinode after\ninitialization. Readers use READ_ONCE() to fetch the pointer.(CVE-2026-31450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: replace BUG_ON with proper error handling in ext4_read_inline_folio\n\nReplace BUG_ON() with proper error handling when inline data size\nexceeds PAGE_SIZE. This prevents kernel panic and allows the system to\ncontinue running while properly reporting the filesystem corruption.\n\nThe error is logged via ext4_error_inode(), the buffer head is released\nto prevent memory leak, and -EFSCORRUPTED is returned to indicate\nfilesystem corruption.(CVE-2026-31451)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: convert inline data to extents when truncate exceeds inline size\n\nAdd a check in ext4_setattr() to convert files from inline data storage\nto extent-based storage when truncate() grows the file size beyond the\ninline capacity. This prevents the filesystem from entering an\ninconsistent state where the inline data flag is set but the file size\nexceeds what can be stored inline.\n\nWithout this fix, the following sequence causes a kernel BUG_ON():\n\n1. Mount filesystem with inode that has inline flag set and small size\n2. truncate(file, 50MB) - grows size but inline flag remains set\n3. sendfile() attempts to write data\n4. ext4_write_inline_data() hits BUG_ON(write_size \u0026gt; inline_capacity)\n\nThe crash occurs because ext4_write_inline_data() expects inline storage\nto accommodate the write, but the actual inline capacity (~60 bytes for\ni_block + ~96 bytes for xattrs) is far smaller than the file size and\nwrite request.\n\nThe fix checks if the new size from setattr exceeds the inode\u0026apos;s actual\ninline capacity (EXT4_I(inode)-\u0026gt;i_inline_size) and converts the file to\nextent-based storage before proceeding with the size change.\n\nThis addresses the root cause by ensuring the inline data flag and file\nsize remain consistent during truncate operations.(CVE-2026-31452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: add GFP_NOIO in the bio completion if needed\n\nThe bio completion path in the process context (e.g. dm-verity)\nwill directly call into decompression rather than trigger another\nworkqueue context for minimal scheduling latencies, which can\nthen call vm_map_ram() with GFP_KERNEL.\n\nDue to insufficient memory, vm_map_ram() may generate memory\nswapping I/O, which can cause submit_bio_wait to deadlock\nin some scenarios.\n\nTrimmed down the call stack, as follows:\n\nf2fs_submit_read_io\n  submit_bio                      //bio_list is initialized.\n    mmc_blk_mq_recovery\n      z_erofs_endio\n        vm_map_ram\n          __pte_alloc_kernel\n            __alloc_pages_direct_reclaim\n              shrink_folio_list\n                __swap_writepage\n                  submit_bio_wait  //bio_list is non-NULL, hang!!!\n\nUse memalloc_noio_{save,restore}() to wrap up this path.(CVE-2026-31467)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n\nA UAF issue occurs when the virtio_net driver is configured with napi_tx=N\nand the device\u0026apos;s IFF_XMIT_DST_RELEASE flag is cleared\n(e.g., during the configuration of tc route filter rules).\n\nWhen IFF_XMIT_DST_RELEASE is removed from the net_device, the network stack\nexpects the driver to hold the reference to skb-\u0026gt;dst until the packet\nis fully transmitted and freed. In virtio_net with napi_tx=N,\nskbs may remain in the virtio transmit ring for an extended period.\n\nIf the network namespace is destroyed while these skbs are still pending,\nthe corresponding dst_ops structure has freed. When a subsequent packet\nis transmitted, free_old_xmit() is triggered to clean up old skbs.\nIt then calls dst_release() on the skb associated with the stale dst_entry.\nSince the dst_ops (referenced by the dst_entry) has already been freed,\na UAF kernel paging request occurs.\n\nfix it by adds skb_dst_drop(skb) in start_xmit to explicitly release\nthe dst reference before the skb is queued in virtio_net.\n\nCall Trace:\n Unable to handle kernel paging request at virtual address ffff80007e150000\n CPU: 2 UID: 0 PID: 6236 Comm: ping Kdump: loaded Not tainted 7.0.0-rc1+ #6 PREEMPT\n  ...\n  percpu_counter_add_batch+0x3c/0x158 lib/percpu_counter.c:98 (P)\n  dst_release+0xe0/0x110  net/core/dst.c:177\n  skb_release_head_state+0xe8/0x108 net/core/skbuff.c:1177\n  sk_skb_reason_drop+0x54/0x2d8 net/core/skbuff.c:1255\n  dev_kfree_skb_any_reason+0x64/0x78 net/core/dev.c:3469\n  napi_consume_skb+0x1c4/0x3a0 net/core/skbuff.c:1527\n  __free_old_xmit+0x164/0x230  drivers/net/virtio_net.c:611 [virtio_net]\n  free_old_xmit drivers/net/virtio_net.c:1081 [virtio_net]\n  start_xmit+0x7c/0x530 drivers/net/virtio_net.c:3329 [virtio_net]\n  ...\n\nReproduction Steps:\nNETDEV=\u0026quot;enp3s0\u0026quot;\n\nconfig_qdisc_route_filter() {\n    tc qdisc del dev $NETDEV root\n    tc qdisc add dev $NETDEV root handle 1: prio\n    tc filter add dev $NETDEV parent 1:0 \\\n\tprotocol ip prio 100 route to 100 flowid 1:1\n    ip route add 192.168.1.100/32 dev $NETDEV realm 100\n}\n\ntest_ns() {\n    ip netns add testns\n    ip link set $NETDEV netns testns\n    ip netns exec testns ifconfig $NETDEV  10.0.32.46/24\n    ip netns exec testns ping -c 1 10.0.32.1\n    ip netns del testns\n}\n\nconfig_qdisc_route_filter\n\ntest_ns\nsleep 2\ntest_ns(CVE-2026-31469)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: use generic driver_override infrastructure\n\nWhen a driver is probed through __driver_attach(), the bus\u0026apos; match()\ncallback is called without the device lock held, thus accessing the\ndriver_override field without a lock, which can cause a UAF.\n\nFix this by using the driver-core driver_override infrastructure taking\ncare of proper locking internally.\n\nNote that calling match() from __driver_attach() without the device lock\nheld is intentional. [1]\n\nAlso note that we do not enable the driver_override feature of struct\nbus_type, as SPI - in contrast to most other buses - passes \u0026quot;\u0026quot; to\nsysfs_emit() when the driver_override pointer is NULL. Thus, printing\n\u0026quot;\\n\u0026quot; instead of \u0026quot;(null)\\n\u0026quot;.(CVE-2026-31487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: use netlink policy range checks\n\nReplace manual range and mask validations with netlink policy\nannotations in ctnetlink code paths, so that the netlink core rejects\ninvalid values early and can generate extack errors.\n\n- CTA_PROTOINFO_TCP_STATE: reject values \u0026gt; TCP_CONNTRACK_SYN_SENT2 at\n  policy level, removing the manual \u0026gt;= TCP_CONNTRACK_MAX check.\n- CTA_PROTOINFO_TCP_WSCALE_ORIGINAL/REPLY: reject values \u0026gt; TCP_MAX_WSCALE\n  (14). The normal TCP option parsing path already clamps to this value,\n  but the ctnetlink path accepted 0-255, causing undefined behavior when\n  used as a u32 shift count.\n- CTA_FILTER_ORIG_FLAGS/REPLY_FLAGS: use NLA_POLICY_MASK with\n  CTA_FILTER_F_ALL, removing the manual mask checks.\n- CTA_EXPECT_FLAGS: use NLA_POLICY_MASK with NF_CT_EXPECT_MASK, adding\n  a new mask define grouping all valid expect flags.\n\nExtracted from a broader nf-next patch by Florian Westphal, scoped to\nctnetlink for the fixes tree.(CVE-2026-31495)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conntrack_expect: skip expectations in other netns via proc\n\nSkip expectations that do not reside in this netns.\n\nSimilar to e77e6ff502ea (\u0026quot;netfilter: conntrack: do not dump other netns\u0026apos;s\nconntrack entries via proc\u0026quot;).(CVE-2026-31496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop\n\nl2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED\nstate to support L2CAP reconfiguration (e.g. MTU changes). However,\nsince both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from\nthe initial configuration, the reconfiguration path falls through to\nl2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and\nretrans_list without freeing the previous allocations and sets\nchan-\u0026gt;sdu to NULL without freeing the existing skb. This leaks all\npreviously allocated ERTM resources.\n\nAdditionally, l2cap_parse_conf_req() does not validate the minimum\nvalue of remote_mps derived from the RFC max_pdu_size option. A zero\nvalue propagates to l2cap_segment_sdu() where pdu_len becomes zero,\ncausing the while loop to never terminate since len is never\ndecremented, exhausting all available memory.\n\nFix the double-init by skipping l2cap_ertm_init() and\nl2cap_chan_ready() when the channel is already in BT_CONNECTED state,\nwhile still allowing the reconfiguration parameters to be updated\nthrough l2cap_parse_conf_req(). Also add a pdu_len zero check in\nl2cap_segment_sdu() as a safeguard.(CVE-2026-31498)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix deadlock in l2cap_conn_del()\n\nl2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer\nand id_addr_timer while holding conn-\u0026gt;lock. However, the work functions\nl2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire\nconn-\u0026gt;lock, creating a potential AB-BA deadlock if the work is already\nexecuting when l2cap_conn_del() takes the lock.\n\nMove the work cancellations before acquiring conn-\u0026gt;lock and use\ndisable_delayed_work_sync() to additionally prevent the works from\nbeing rearmed after cancellation, consistent with the pattern used in\nhci_conn_del().(CVE-2026-31499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix out-of-bounds writes in iavf_get_ethtool_stats()\n\niavf incorrectly uses real_num_tx_queues for ETH_SS_STATS. Since the\nvalue could change in runtime, we should use num_tx_queues instead.\n\nMoreover iavf_get_ethtool_stats() uses num_active_queues while\niavf_get_sset_count() and iavf_get_stat_strings() use\nreal_num_tx_queues, which triggers out-of-bounds writes when we do\n\u0026quot;ethtool -L\u0026quot; and \u0026quot;ethtool -S\u0026quot; simultaneously [1].\n\nFor example when we change channels from 1 to 8, Thread 3 could be\nscheduled before Thread 2, and out-of-bounds writes could be triggered\nin Thread 3:\n\nThread 1 (ethtool -L)       Thread 2 (work)        Thread 3 (ethtool -S)\niavf_set_channels()\n...\niavf_alloc_queues()\n-\u0026gt; num_active_queues = 8\niavf_schedule_finish_config()\n                                                   iavf_get_sset_count()\n                                                   real_num_tx_queues: 1\n                                                   -\u0026gt; buffer for 1 queue\n                                                   iavf_get_ethtool_stats()\n                                                   num_active_queues: 8\n                                                   -\u0026gt; out-of-bounds!\n                            iavf_finish_config()\n                            -\u0026gt; real_num_tx_queues = 8\n\nUse immutable num_tx_queues in all related functions to avoid the issue.\n\n[1]\n BUG: KASAN: vmalloc-out-of-bounds in iavf_add_one_ethtool_stat+0x200/0x270\n Write of size 8 at addr ffffc900031c9080 by task ethtool/5800\n\n CPU: 1 UID: 0 PID: 5800 Comm: ethtool Not tainted 6.19.0-enjuk-08403-g8137e3db7f1c #241 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x6f/0xb0\n  print_report+0x170/0x4f3\n  kasan_report+0xe1/0x180\n  iavf_add_one_ethtool_stat+0x200/0x270\n  iavf_get_ethtool_stats+0x14c/0x2e0\n  __dev_ethtool+0x3d0c/0x5830\n  dev_ethtool+0x12d/0x270\n  dev_ioctl+0x53c/0xe30\n  sock_do_ioctl+0x1a9/0x270\n  sock_ioctl+0x3d4/0x5e0\n  __x64_sys_ioctl+0x137/0x1c0\n  do_syscall_64+0xf3/0x690\n  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n RIP: 0033:0x7f7da0e6e36d\n ...\n  \u0026lt;/TASK\u0026gt;\n\n The buggy address belongs to a 1-page vmalloc region starting at 0xffffc900031c9000 allocated at __dev_ethtool+0x3cc9/0x5830\n The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000\n index:0xffff88813a013de0 pfn:0x13a013\n flags: 0x200000000000000(node=0|zone=2)\n raw: 0200000000000000 0000000000000000 dead000000000122 0000000000000000\n raw: ffff88813a013de0 0000000000000000 00000001ffffffff 0000000000000000\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n  ffffc900031c8f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n \u0026gt;ffffc900031c9080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n                    ^\n  ffffc900031c9100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n  ffffc900031c9180: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8(CVE-2026-31505)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb\n\nBefore using sk pointer, check if it is null.\n\nFix the following:\n\n KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267]\n CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025\n Workqueue: events l2cap_info_timeout\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n veth0_macvtap: entered promiscuous mode\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  __kasan_check_byte+0x12/0x40\n  lock_acquire+0x79/0x2e0\n  lock_sock_nested+0x48/0x100\n  ? l2cap_sock_ready_cb+0x46/0x160\n  l2cap_sock_ready_cb+0x46/0x160\n  l2cap_conn_start+0x779/0xff0\n  ? __pfx_l2cap_conn_start+0x10/0x10\n  ? l2cap_info_timeout+0x60/0xa0\n  ? __pfx___mutex_lock+0x10/0x10\n  l2cap_info_timeout+0x68/0xa0\n  ? process_scheduled_works+0xa8d/0x18c0\n  process_scheduled_works+0xb6e/0x18c0\n  ? __pfx_process_scheduled_works+0x10/0x10\n  ? assign_work+0x3d5/0x5e0\n  worker_thread+0xa53/0xfc0\n  kthread+0x388/0x470\n  ? __pfx_worker_thread+0x10/0x10\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x51e/0xb90\n  ? __pfx_ret_from_fork+0x10/0x10\n veth1_macvtap: entered promiscuous mode\n  ? __switch_to+0xc7d/0x1450\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u0026lt;/TASK\u0026gt;\n Modules linked in:\n ---[ end trace 0000000000000000 ]---\n batman_adv: batadv0: Interface activated: batadv_slave_0\n batman_adv: batadv0: Interface activated: batadv_slave_1\n netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n ieee80211 phy39: Selected rate control algorithm \u0026apos;minstrel_ht\u0026apos;\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS:  0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Kernel panic - not syncing: Fatal exception(CVE-2026-31510)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete\n\nThis fixes the condition checking so mgmt_pending_valid is executed\nwhenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd)\nwould kfree(cmd) without unlinking it from the list first, leaving a\ndangling pointer. Any subsequent list traversal (e.g.,\nmgmt_pending_foreach during __mgmt_power_off, or another\nmgmt_pending_valid call) would dereference freed memory.(CVE-2026-31511)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n\nl2cap_ecred_data_rcv() reads the SDU length field from skb-\u0026gt;data using\nget_unaligned_le16() without first verifying that skb contains at least\nL2CAP_SDULEN_SIZE (2) bytes. When skb-\u0026gt;len is less than 2, this reads\npast the valid data in the skb.\n\nThe ERTM reassembly path correctly calls pskb_may_pull() before reading\nthe SDU length (l2cap_reassemble_sdu, L2CAP_SAR_START case). Apply the\nsame validation to the Enhanced Credit Based Flow Control data path.(CVE-2026-31512)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: prevent policy_hthresh.work from racing with netns teardown\n\nA XFRM_MSG_NEWSPDINFO request can queue the per-net work item\npolicy_hthresh.work onto the system workqueue.\n\nThe queued callback, xfrm_hash_rebuild(), retrieves the enclosing\nstruct net via container_of(). If the net namespace is torn down\nbefore that work runs, the associated struct net may already have\nbeen freed, and xfrm_hash_rebuild() may then dereference stale memory.\n\nxfrm_policy_fini() already flushes policy_hash_work during teardown,\nbut it does not synchronize policy_hthresh.work.\n\nSynchronize policy_hthresh.work in xfrm_policy_fini() as well, so the\nqueued work cannot outlive the net namespace teardown and access a\nfreed struct net.(CVE-2026-31516)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nesp: fix skb leak with espintcp and async crypto\n\nWhen the TX queue for espintcp is full, esp_output_tail_tcp will\nreturn an error and not free the skb, because with synchronous crypto,\nthe common xfrm output code will drop the packet for us.\n\nWith async crypto (esp_output_done), we need to drop the skb when\nesp_output_tail_tcp returns an error.(CVE-2026-31518)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN\n\nThe BPF interpreter\u0026apos;s signed 32-bit division and modulo handlers use\nthe kernel abs() macro on s32 operands. The abs() macro documentation\n(include/linux/math.h) explicitly states the result is undefined when\nthe input is the type minimum. When DST contains S32_MIN (0x80000000),\nabs((s32)DST) triggers undefined behavior and returns S32_MIN unchanged\non arm64/x86. This value is then sign-extended to u64 as\n0xFFFFFFFF80000000, causing do_div() to compute the wrong result.\n\nThe verifier\u0026apos;s abstract interpretation (scalar32_min_max_sdiv) computes\nthe mathematically correct result for range tracking, creating a\nverifier/interpreter mismatch that can be exploited for out-of-bounds\nmap value access.\n\nIntroduce abs_s32() which handles S32_MIN correctly by casting to u32\nbefore negating, avoiding signed overflow entirely. Replace all 8\nabs((s32)...) call sites in the interpreter\u0026apos;s sdiv32/smod32 handlers.\n\ns32 is the only affected case -- the s64 division/modulo handlers do\nnot use abs().(CVE-2026-31525)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Make sure to use pmu_ctx-\u0026gt;pmu for groups\n\nOliver reported that x86_pmu_del() ended up doing an out-of-bound memory access\nwhen group_sched_in() fails and needs to roll back.\n\nThis *should* be handled by the transaction callbacks, but he found that when\nthe group leader is a software event, the transaction handlers of the wrong PMU\nare used. Despite the move_group case in perf_event_open() and group_sched_in()\nusing pmu_ctx-\u0026gt;pmu.\n\nTurns out, inherit uses event-\u0026gt;pmu to clone the events, effectively undoing the\nmove_group case for all inherited contexts. Fix this by also making inherit use\npmu_ctx-\u0026gt;pmu, ensuring all inherited counters end up in the same pmu context.\n\nSimilarly, __perf_event_read() should use equally use pmu_ctx-\u0026gt;pmu for the\ngroup case.(CVE-2026-31528)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: nexthop: allocate skb dynamically in rtm_get_nexthop()\n\nWhen querying a nexthop object via RTM_GETNEXTHOP, the kernel currently\nallocates a fixed-size skb using NLMSG_GOODSIZE. While sufficient for\nsingle nexthops and small Equal-Cost Multi-Path groups, this fixed\nallocation fails for large nexthop groups like 512 nexthops.\n\nThis results in the following warning splat:\n\n WARNING: net/ipv4/nexthop.c:3395 at rtm_get_nexthop+0x176/0x1c0, CPU#20: rep/4608\n [...]\n RIP: 0010:rtm_get_nexthop (net/ipv4/nexthop.c:3395)\n [...]\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  rtnetlink_rcv_msg (net/core/rtnetlink.c:6989)\n  netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n  netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n  netlink_sendmsg (net/netlink/af_netlink.c:1894)\n  ____sys_sendmsg (net/socket.c:721 net/socket.c:736 net/socket.c:2585)\n  ___sys_sendmsg (net/socket.c:2641)\n  __sys_sendmsg (net/socket.c:2671)\n  do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\n  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n  \u0026lt;/TASK\u0026gt;\n\nFix this by allocating the size dynamically using nh_nlmsg_size() and\nusing nlmsg_new(), this is consistent with nexthop_notify() behavior. In\naddition, adjust nh_nlmsg_size_grp() so it calculates the size needed\nbased on flags passed. While at it, also add the size of NHA_FDB for\nnexthop group size calculation as it was missing too.\n\nThis cannot be reproduced via iproute2 as the group size is currently\nlimited and the command fails as follows:\n\naddattr_l ERROR: message exceeded bound of 1048(CVE-2026-31531)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw: fix ro-\u0026gt;uniq use-after-free in raw_rcv()\n\nraw_release() unregisters raw CAN receive filters via can_rx_unregister(),\nbut receiver deletion is deferred with call_rcu(). This leaves a window\nwhere raw_rcv() may still be running in an RCU read-side critical section\nafter raw_release() frees ro-\u0026gt;uniq, leading to a use-after-free of the\npercpu uniq storage.\n\nMove free_percpu(ro-\u0026gt;uniq) out of raw_release() and into a raw-specific\nsocket destructor. can_rx_unregister() takes an extra reference to the\nsocket and only drops it from the RCU callback, so freeing uniq from\nsk_destruct ensures the percpu area is not released until the relevant\ncallbacks have drained.\n\n[mkl: applied manually](CVE-2026-31532)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: fix use-after-free in -EBUSY error path of tls_do_encryption\n\nThe -EBUSY handling in tls_do_encryption(), introduced by commit\n859054147318 (\u0026quot;net: tls: handle backlogging of crypto requests\u0026quot;), has\na use-after-free due to double cleanup of encrypt_pending and the\nscatterlist entry.\n\nWhen crypto_aead_encrypt() returns -EBUSY, the request is enqueued to\nthe cryptd backlog and the async callback tls_encrypt_done() will be\ninvoked upon completion. That callback unconditionally restores the\nscatterlist entry (sge-\u0026gt;offset, sge-\u0026gt;length) and decrements\nctx-\u0026gt;encrypt_pending. However, if tls_encrypt_async_wait() returns an\nerror, the synchronous error path in tls_do_encryption() performs the\nsame cleanup again, double-decrementing encrypt_pending and\ndouble-restoring the scatterlist.\n\nThe double-decrement corrupts the encrypt_pending sentinel (initialized\nto 1), making tls_encrypt_async_wait() permanently skip the wait for\npending async callbacks. A subsequent sendmsg can then free the\ntls_rec via bpf_exec_tx_verdict() while a cryptd callback is still\npending, resulting in a use-after-free when the callback fires on the\nfreed record.\n\nFix this by skipping the synchronous cleanup when the -EBUSY async\nwait returns an error, since the callback has already handled\nencrypt_pending and sge restoration.(CVE-2026-31533)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gt: Check set_default_submission() before deferencing\n\nWhen the i915 driver firmware binaries are not present, the\nset_default_submission pointer is not set. This pointer is\ndereferenced during suspend anyways.\n\nAdd a check to make sure it is set before dereferencing.\n\n[   23.289926] PM: suspend entry (deep)\n[   23.293558] Filesystems sync: 0.000 seconds\n[   23.298010] Freezing user space processes\n[   23.302771] Freezing user space processes completed (elapsed 0.000 seconds)\n[   23.309766] OOM killer disabled.\n[   23.313027] Freezing remaining freezable tasks\n[   23.318540] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)\n[   23.342038] serial 00:05: disabled\n[   23.345719] serial 00:02: disabled\n[   23.349342] serial 00:01: disabled\n[   23.353782] sd 0:0:0:0: [sda] Synchronizing SCSI cache\n[   23.358993] sd 1:0:0:0: [sdb] Synchronizing SCSI cache\n[   23.361635] ata1.00: Entering standby power mode\n[   23.368863] ata2.00: Entering standby power mode\n[   23.445187] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[   23.452194] #PF: supervisor instruction fetch in kernel mode\n[   23.457896] #PF: error_code(0x0010) - not-present page\n[   23.463065] PGD 0 P4D 0\n[   23.465640] Oops: Oops: 0010 [#1] SMP NOPTI\n[   23.469869] CPU: 8 UID: 0 PID: 211 Comm: kworker/u48:18 Tainted: G S      W           6.19.0-rc4-00020-gf0b9d8eb98df #10 PREEMPT(voluntary)\n[   23.482512] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN\n[   23.496511] Workqueue: async async_run_entry_fn\n[   23.501087] RIP: 0010:0x0\n[   23.503755] Code: Unable to access opcode bytes at 0xffffffffffffffd6.\n[   23.510324] RSP: 0018:ffffb4a60065fca8 EFLAGS: 00010246\n[   23.515592] RAX: 0000000000000000 RBX: ffff9f428290e000 RCX: 000000000000000f\n[   23.522765] RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffff9f428290e000\n[   23.529937] RBP: ffff9f4282907070 R08: ffff9f4281130428 R09: 00000000ffffffff\n[   23.537111] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f42829070f8\n[   23.544284] R13: ffff9f4282906028 R14: ffff9f4282900000 R15: ffff9f4282906b68\n[   23.551457] FS:  0000000000000000(0000) GS:ffff9f466b2cf000(0000) knlGS:0000000000000000\n[   23.559588] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   23.565365] CR2: ffffffffffffffd6 CR3: 000000031c230001 CR4: 0000000000f70ef0\n[   23.572539] PKRU: 55555554\n[   23.575281] Call Trace:\n[   23.577770]  \u0026lt;TASK\u0026gt;\n[   23.579905]  intel_engines_reset_default_submission+0x42/0x60\n[   23.585695]  __intel_gt_unset_wedged+0x191/0x200\n[   23.590360]  intel_gt_unset_wedged+0x20/0x40\n[   23.594675]  gt_sanitize+0x15e/0x170\n[   23.598290]  i915_gem_suspend_late+0x6b/0x180\n[   23.602692]  i915_drm_suspend_late+0x35/0xf0\n[   23.607008]  ? __pfx_pci_pm_suspend_late+0x10/0x10\n[   23.611843]  dpm_run_callback+0x78/0x1c0\n[   23.615817]  device_suspend_late+0xde/0x2e0\n[   23.620037]  async_suspend_late+0x18/0x30\n[   23.624082]  async_run_entry_fn+0x25/0xa0\n[   23.628129]  process_one_work+0x15b/0x380\n[   23.632182]  worker_thread+0x2a5/0x3c0\n[   23.635973]  ? __pfx_worker_thread+0x10/0x10\n[   23.640279]  kthread+0xf6/0x1f0\n[   23.643464]  ? __pfx_kthread+0x10/0x10\n[   23.647263]  ? __pfx_kthread+0x10/0x10\n[   23.651045]  ret_from_fork+0x131/0x190\n[   23.654837]  ? __pfx_kthread+0x10/0x10\n[   23.658634]  ret_from_fork_asm+0x1a/0x30\n[   23.662597]  \u0026lt;/TASK\u0026gt;\n[   23.664826] Modules linked in:\n[   23.667914] CR2: 0000000000000000\n[   23.671271] ------------[ cut here ]------------\n\n(cherry picked from commit daa199abc3d3d1740c9e3a2c3e9216ae5b447cad)(CVE-2026-31540)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/platform/uv: Handle deconfigured sockets\n\nWhen a socket is deconfigured, it\u0026apos;s mapped to SOCK_EMPTY (0xffff). This causes\na panic while allocating UV hub info structures.\n\nFix this by using NUMA_NO_NODE, allowing UV hub info structures to be\nallocated on valid nodes.(CVE-2026-31542)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix NULL deref in bond_debug_rlb_hash_show\n\nrlb_clear_slave intentionally keeps RLB hash-table entries on\nthe rx_hashtbl_used_head list with slave set to NULL when no\nreplacement slave is available. However, bond_debug_rlb_hash_show\nvisites client_info-\u0026gt;slave without checking if it\u0026apos;s NULL.\n\nOther used-list iterators in bond_alb.c already handle this NULL-slave\nstate safely:\n\n- rlb_update_client returns early on !client_info-\u0026gt;slave\n- rlb_req_update_slave_clients, rlb_clear_slave, and rlb_rebalance\ncompare slave values before visiting\n- lb_req_update_subnet_clients continues if slave is NULL\n\nThe following NULL deref crash can be trigger in\nbond_debug_rlb_hash_show:\n\n[    1.289791] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[    1.292058] RIP: 0010:bond_debug_rlb_hash_show (drivers/net/bonding/bond_debugfs.c:41)\n[    1.293101] RSP: 0018:ffffc900004a7d00 EFLAGS: 00010286\n[    1.293333] RAX: 0000000000000000 RBX: ffff888102b48200 RCX: ffff888102b48204\n[    1.293631] RDX: ffff888102b48200 RSI: ffffffff839daad5 RDI: ffff888102815078\n[    1.293924] RBP: ffff888102815078 R08: ffff888102b4820e R09: 0000000000000000\n[    1.294267] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100f929c0\n[    1.294564] R13: ffff888100f92a00 R14: 0000000000000001 R15: ffffc900004a7ed8\n[    1.294864] FS:  0000000001395380(0000) GS:ffff888196e75000(0000) knlGS:0000000000000000\n[    1.295239] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    1.295480] CR2: 0000000000000000 CR3: 0000000102adc004 CR4: 0000000000772ef0\n[    1.295897] Call Trace:\n[    1.296134]  seq_read_iter (fs/seq_file.c:231)\n[    1.296341]  seq_read (fs/seq_file.c:164)\n[    1.296493]  full_proxy_read (fs/debugfs/file.c:378 (discriminator 1))\n[    1.296658]  vfs_read (fs/read_write.c:572)\n[    1.296981]  ksys_read (fs/read_write.c:717)\n[    1.297132]  do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n[    1.297325]  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\nAdd a NULL check and print \u0026quot;(none)\u0026quot; for entries with no assigned slave.(CVE-2026-31546)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Clear stale exiting pointer in futex_lock_pi() retry path\n\nFuzzying/stressing futexes triggered:\n\n    WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524\n\nWhen futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY\nand stores a refcounted task pointer in \u0026apos;exiting\u0026apos;.\n\nAfter wait_for_owner_exiting() consumes that reference, the local pointer\nis never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a\ndifferent error, the bogus pointer is passed to wait_for_owner_exiting().\n\n  CPU0\t\t\t     CPU1\t\t       CPU2\n  futex_lock_pi(uaddr)\n  // acquires the PI futex\n  exit()\n    futex_cleanup_begin()\n      futex_state = EXITING;\n\t\t\t     futex_lock_pi(uaddr)\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t attach_to_pi_owner()\n\t\t\t\t   // observes EXITING\n\t\t\t\t   *exiting = owner;  // takes ref\n\t\t\t\t   return -EBUSY\n\t\t\t       wait_for_owner_exiting(-EBUSY, owner)\n\t\t\t\t put_task_struct();   // drops ref\n\t\t\t       // exiting still points to owner\n\t\t\t       goto retry;\n\t\t\t       futex_lock_pi_atomic()\n\t\t\t\t lock_pi_update_atomic()\n\t\t\t\t   cmpxchg(uaddr)\n\t\t\t\t\t*uaddr ^= WAITERS // whatever\n\t\t\t\t   // value changed\n\t\t\t\t return -EAGAIN;\n\t\t\t       wait_for_owner_exiting(-EAGAIN, exiting) // stale\n\t\t\t\t WARN_ON_ONCE(exiting)\n\nFix this by resetting upon retry, essentially aligning it with requeue_pi.(CVE-2026-31555)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib\n\namdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence\nfrom amdgpu_ib_schedule(). This fence is used to wait for job\ncompletion.\n\nCurrently, the code drops the fence reference using dma_fence_put()\nbefore calling dma_fence_wait().\n\nIf dma_fence_put() releases the last reference, the fence may be\nfreed before dma_fence_wait() is called. This can lead to a\nuse-after-free.\n\nFix this by waiting on the fence first and releasing the reference\nonly after dma_fence_wait() completes.\n\nFixes the below:\ndrivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory \u0026apos;f\u0026apos; (line 696)\n\n(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)(CVE-2026-31566)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: gw: fix OOB heap access in cgw_csum_crc8_rel()\n\ncgw_csum_crc8_rel() correctly computes bounds-safe indices via calc_idx():\n\n    int from = calc_idx(crc8-\u0026gt;from_idx, cf-\u0026gt;len);\n    int to   = calc_idx(crc8-\u0026gt;to_idx,   cf-\u0026gt;len);\n    int res  = calc_idx(crc8-\u0026gt;result_idx, cf-\u0026gt;len);\n\n    if (from \u0026lt; 0 || to \u0026lt; 0 || res \u0026lt; 0)\n        return;\n\nHowever, the loop and the result write then use the raw s8 fields directly\ninstead of the computed variables:\n\n    for (i = crc8-\u0026gt;from_idx; ...)        /* BUG: raw negative index */\n    cf-\u0026gt;data[crc8-\u0026gt;result_idx] = ...;    /* BUG: raw negative index */\n\nWith from_idx = to_idx = result_idx = -64 on a 64-byte CAN FD frame,\ncalc_idx(-64, 64) = 0 so the guard passes, but the loop iterates with\ni = -64, reading cf-\u0026gt;data[-64], and the write goes to cf-\u0026gt;data[-64].\nThis write might end up to 56 (7.0-rc) or 40 (\u0026lt;= 6.19) bytes before the\nstart of the canfd_frame on the heap.\n\nThe companion function cgw_csum_xor_rel() uses `from`/`to`/`res`\ncorrectly throughout; fix cgw_csum_crc8_rel() to match.\n\nConfirmed with KASAN on linux-7.0-rc2:\n  BUG: KASAN: slab-out-of-bounds in cgw_csum_crc8_rel+0x515/0x5b0\n  Read of size 1 at addr ffff8880076619c8 by task poc_cgw_oob/62\n\nTo configure the can-gw crc8 checksums CAP_NET_ADMIN is needed.(CVE-2026-31570)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION\n\nDrop the WARN in sev_pin_memory() on npages overflowing an int, as the\nWARN is comically trivially to trigger from userspace, e.g. by doing:\n\n  struct kvm_enc_region range = {\n          .addr = 0,\n          .size = -1ul,\n  };\n\n  __vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, \u0026amp;range);\n\nNote, the checks in sev_mem_enc_register_region() that presumably exist to\nverify the incoming address+size are completely worthless, as both \u0026quot;addr\u0026quot;\nand \u0026quot;size\u0026quot; are u64s and SEV is 64-bit only, i.e. they _can\u0026apos;t_ be greater\nthan ULONG_MAX.  That wart will be cleaned up in the near future.\n\n\tif (range-\u0026gt;addr \u0026gt; ULONG_MAX || range-\u0026gt;size \u0026gt; ULONG_MAX)\n\t\treturn -EINVAL;\n\nOpportunistically add a comment to explain why the code calculates the\nnumber of pages the \u0026quot;hard\u0026quot; way, e.g. instead of just shifting @ulen.(CVE-2026-31590)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup\n\nDisable the delayed work before clearing BAR mappings and doorbells to\navoid running the handler after resources have been torn down.\n\n  Unable to handle kernel paging request at virtual address ffff800083f46004\n  [...]\n  Internal error: Oops: 0000000096000007 [#1]  SMP\n  [...]\n  Call trace:\n   epf_ntb_cmd_handler+0x54/0x200 [pci_epf_vntb] (P)\n   process_one_work+0x154/0x3b0\n   worker_thread+0x2c8/0x400\n   kthread+0x148/0x210\n   ret_from_fork+0x10/0x20(CVE-2026-31595)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU: Fix FPDSS on Zen1\n\nZen1\u0026apos;s hardware divider can leave, under certain circumstances, partial\nresults from previous operations.  Those results can be leaked by\nanother, attacker thread.\n\nFix that with a chicken bit.(CVE-2026-31628)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: proc: size address buffers for %pISpc output\n\nThe AF_RXRPC procfs helpers format local and remote socket addresses into\nfixed 50-byte stack buffers with \u0026quot;%pISpc\u0026quot;.\n\nThat is too small for the longest current-tree IPv6-with-port form the\nformatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a\ndotted-quad tail not only for v4mapped addresses, but also for ISATAP\naddresses via ipv6_addr_is_isatap().\n\nAs a result, a case such as\n\n  [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535\n\nis possible with the current formatter. That is 50 visible characters, so\n51 bytes including the trailing NUL, which does not fit in the existing\nchar[50] buffers used by net/rxrpc/proc.c.\n\nSize the buffers from the formatter\u0026apos;s maximum textual form and switch the\ncall sites to scnprintf().\n\nChanges since v1:\n- correct the changelog to cite the actual maximum current-tree case\n  explicitly\n- frame the proof around the ISATAP formatting path instead of the earlier\n  mapped-v4 example(CVE-2026-31630)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmmc: vub300: fix NULL-deref on disconnect\n\nMake sure to deregister the controller before dropping the reference to\nthe driver data on disconnect to avoid NULL-pointer dereferences or\nuse-after-free.(CVE-2026-31651)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: fix use-after-free in timeout object destroy\n\nnft_ct_timeout_obj_destroy() frees the timeout object with kfree()\nimmediately after nf_ct_untimeout(), without waiting for an RCU grace\nperiod. Concurrent packet processing on other CPUs may still hold\nRCU-protected references to the timeout object obtained via\nrcu_dereference() in nf_ct_timeout_data().\n\nAdd an rcu_head to struct nf_ct_timeout and use kfree_rcu() to defer\nfreeing until after an RCU grace period, matching the approach already\nused in nfnetlink_cttimeout.c.\n\nKASAN report:\n BUG: KASAN: slab-use-after-free in nf_conntrack_tcp_packet+0x1381/0x29d0\n Read of size 4 at addr ffff8881035fe19c by task exploit/80\n\n Call Trace:\n  nf_conntrack_tcp_packet+0x1381/0x29d0\n  nf_conntrack_in+0x612/0x8b0\n  nf_hook_slow+0x70/0x100\n  __ip_local_out+0x1b2/0x210\n  tcp_sendmsg_locked+0x722/0x1580\n  __sys_sendto+0x2d8/0x320\n\n Allocated by task 75:\n  nft_ct_timeout_obj_init+0xf6/0x290\n  nft_obj_init+0x107/0x1b0\n  nf_tables_newobj+0x680/0x9c0\n  nfnetlink_rcv_batch+0xc29/0xe00\n\n Freed by task 26:\n  nft_obj_destroy+0x3f/0xa0\n  nf_tables_trans_destroy_work+0x51c/0x5c0\n  process_one_work+0x2c4/0x5a0(CVE-2026-31665)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: uinput - fix circular locking dependency with ff-core\n\nA lockdep circular locking dependency warning can be triggered\nreproducibly when using a force-feedback gamepad with uinput (for\nexample, playing ELDEN RING under Wine with a Flydigi Vader 5\ncontroller):\n\n  ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex\n\nThe cycle is caused by four lock acquisition paths:\n\n1. ff upload: input_ff_upload() holds ff-\u0026gt;mutex and calls\n   uinput_dev_upload_effect() -\u0026gt; uinput_request_submit() -\u0026gt;\n   uinput_request_send(), which acquires udev-\u0026gt;mutex.\n\n2. device create: uinput_ioctl_handler() holds udev-\u0026gt;mutex and calls\n   uinput_create_device() -\u0026gt; input_register_device(), which acquires\n   input_mutex.\n\n3. device register: input_register_device() holds input_mutex and\n   calls kbd_connect() -\u0026gt; input_register_handle(), which acquires\n   dev-\u0026gt;mutex.\n\n4. evdev release: evdev_release() calls input_flush_device() under\n   dev-\u0026gt;mutex, which calls input_ff_flush() acquiring ff-\u0026gt;mutex.\n\nFix this by introducing a new state_lock spinlock to protect\nudev-\u0026gt;state and udev-\u0026gt;dev access in uinput_request_send() instead of\nacquiring udev-\u0026gt;mutex.  The function only needs to atomically check\ndevice state and queue an input event into the ring buffer via\nuinput_dev_event() -- both operations are safe under a spinlock\n(ktime_get_ts64() and wake_up_interruptible() do not sleep).  This\nbreaks the ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex link since a spinlock is a leaf in\nthe lock ordering and cannot form cycles with mutexes.\n\nTo keep state transitions visible to uinput_request_send(), protect\nwrites to udev-\u0026gt;state in uinput_create_device() and\nuinput_destroy_device() with the same state_lock spinlock.\n\nAdditionally, move init_completion(\u0026amp;request-\u0026gt;done) from\nuinput_request_send() to uinput_request_submit() before\nuinput_request_reserve_slot().  Once the slot is allocated,\nuinput_flush_requests() may call complete() on it at any time from\nthe destroy path, so the completion must be initialised before the\nrequest becomes visible.\n\nLock ordering after the fix:\n\n  ff-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n  udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex (no back-edge)(CVE-2026-31667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_netem: fix out-of-bounds access in packet corruption\n\nIn netem_enqueue(), the packet corruption logic uses\nget_random_u32_below(skb_headlen(skb)) to select an index for\nmodifying skb-\u0026gt;data. When an AF_PACKET TX_RING sends fully non-linear\npackets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.\n\nPassing 0 to get_random_u32_below() takes the variable-ceil slow path\nwhich returns an unconstrained 32-bit random integer. Using this\nunconstrained value as an offset into skb-\u0026gt;data results in an\nout-of-bounds memory access.\n\nFix this by verifying skb_headlen(skb) is non-zero before attempting\nto corrupt the linear data area. Fully non-linear packets will silently\nbypass the corruption logic.(CVE-2026-31675)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - limit RX SG extraction by receive buffer budget\n\nMake af_alg_get_rsgl() limit each RX scatterlist extraction to the\nremaining receive buffer budget.\n\naf_alg_get_rsgl() currently uses af_alg_readable() only as a gate\nbefore extracting data into the RX scatterlist. Limit each extraction\nto the remaining af_alg_rcvbuf(sk) budget so that receive-side\naccounting matches the amount of data attached to the request.\n\nIf skcipher cannot obtain enough RX space for at least one chunk while\nmore data remains to be processed, reject the recvmsg call instead of\nrounding the request length down to zero.(CVE-2026-31677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: defer tunnel netdev_put to RCU release\n\novs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already\ndetached the device. Dropping the netdev reference in destroy can race\nwith concurrent readers that still observe vport-\u0026gt;dev.\n\nDo not release vport-\u0026gt;dev in ovs_netdev_tunnel_destroy(). Instead, let\nvport_netdev_free() drop the reference from the RCU callback, matching\nthe non-tunnel destroy path and avoiding additional synchronization\nunder RTNL.(CVE-2026-31678)\n\nIn the Linux kernel, a memory out-of-bounds access vulnerability exists in the act_csum module\u0026apos;s tcf_csum_act() function when processing nested VLAN headers. When an skb still carries in-payload VLAN tags, the function walks nested VLAN headers directly from skb-\u0026gt;data. The current code reads vlan-\u0026gt;h_vlan_encapsulated_proto and then pulls VLAN_HLEN bytes without first ensuring that the full VLAN header is present in the linear area. If only part of an inner VLAN header is linearized, accessing h_vlan_encapsulated_proto reads past the linear area, and the following skb_pull(VLAN_HLEN) may violate skb invariants.(CVE-2026-31684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ip6t_eui64: reject invalid MAC header for all packets\n\n`eui64_mt6()` derives a modified EUI-64 from the Ethernet source address\nand compares it with the low 64 bits of the IPv6 source address.\n\nThe existing guard only rejects an invalid MAC header when\n`par-\u0026gt;fragoff != 0`. For packets with `par-\u0026gt;fragoff == 0`, `eui64_mt6()`\ncan still reach `eth_hdr(skb)` even when the MAC header is not valid.\n\nFix this by removing the `par-\u0026gt;fragoff != 0` condition so that packets\nwith an invalid MAC header are rejected before accessing `eth_hdr(skb)`.(CVE-2026-31685)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u0026gt;pvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device\u0026apos;s release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they\u0026apos;re called:\n\n  MCE: In-kernel MCE decoding enabled.\n  ------------[ cut here ]------------\n  kobject: \u0026apos;(null)\u0026apos;: is not initialized, yet kobject_put() is being called.\n  WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n  CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n  RIP: 0010:kobject_put\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   edac_mc_alloc+0xbe/0xe0 [edac_core]\n   amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n   ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n   do_one_initcall\n   ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.(CVE-2026-31689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy ID to userspace if PSP command failed\n\nWhen retrieving the ID for the CPU, don\u0026apos;t attempt to copy the ID blob to\nuserspace if the firmware command failed.  If the failure was due to an\ninvalid length, i.e. the userspace buffer+length was too small, copying\nthe number of bytes _firmware_ requires will overflow the kernel-allocated\nbuffer and leak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 64 at addr ffff8881867f5960 by task syz.0.906/24388\n\n  CPU: 130 UID: 0 PID: 24388 Comm: syz.0.906 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_get_id2+0x361/0x490 ../drivers/crypto/ccp/sev-dev.c:2222\n   sev_ioctl+0x25f/0x490 ../drivers/crypto/ccp/sev-dev.c:2575\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy PDH cert to userspace if PSP command failed\n\nWhen retrieving the PDH cert, don\u0026apos;t attempt to copy the blobs to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff8885c4ab8aa0 by task syz.0.186/21033\n\n  CPU: 51 UID: 0 PID: 21033 Comm: syz.0.186 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc.                                                       Arcadia_IT_80/Arcadia_IT_80, BIOS 34.84.12-0 11/17/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pdh_export+0x3d3/0x7c0 ../drivers/crypto/ccp/sev-dev.c:2347\n   sev_ioctl+0x2a2/0x490 ../drivers/crypto/ccp/sev-dev.c:2568\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31698)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy CSR to userspace if PSP command failed\n\nWhen retrieving the PEK CSR, don\u0026apos;t attempt to copy the blob to userspace\nif the firmware command failed.  If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n  BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n  BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n  BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n  Read of size 2084 at addr ffff898144612e20 by task syz.9.219/21405\n\n  CPU: 14 UID: 0 PID: 21405 Comm: syz.9.219 Tainted: G     U     O        7.0.0-smp-DEV #28 PREEMPTLAZY\n  Tainted: [U]=USER, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n   print_address_description ../mm/kasan/report.c:378 [inline]\n   print_report+0xbc/0x260 ../mm/kasan/report.c:482\n   kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n   check_region_inline ../mm/kasan/generic.c:-1 [inline]\n   kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n   instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n   _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n   _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n   copy_to_user ../include/linux/uaccess.h:236 [inline]\n   sev_ioctl_do_pek_csr+0x31f/0x590 ../drivers/crypto/ccp/sev-dev.c:1872\n   sev_ioctl+0x3a4/0x490 ../drivers/crypto/ccp/sev-dev.c:2562\n   vfs_ioctl ../fs/ioctl.c:51 [inline]\n   __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n   __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n   do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n   do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n   \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path\n\nsmb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL\nand the default QUERY_INFO path.  The QUERY_INFO branch clamps\nqi.input_buffer_length to the server-reported OutputBufferLength and then\ncopies qi.input_buffer_length bytes from qi_rsp-\u0026gt;Buffer to userspace, but\nit never verifies that the flexible-array payload actually fits within\nrsp_iov[1].iov_len.\n\nA malicious server can return OutputBufferLength larger than the actual\nQUERY_INFO response, causing copy_to_user() to walk past the response\nbuffer and expose adjacent kernel heap to userspace.\n\nGuard the QUERY_INFO copy with a bounds check on the actual Buffer\npayload.  Use struct_size(qi_rsp, Buffer, qi.input_buffer_length)\nrather than an open-coded addition so the guard cannot overflow on\n32-bit builds.(CVE-2026-31708)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: validate ND option lengths in vxlan_na_create\n\nvxlan_na_create() walks ND options according to option-provided\nlengths. A malformed option can make the parser advance beyond the\ncomputed option span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31738)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: br_nd_send: validate ND option lengths\n\nbr_nd_send() walks ND options according to option-provided lengths.\nA malformed option can make the parser advance beyond the computed\noption span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31752)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: fix NULL pointer dereference in ep_queue\n\nWhen the gadget endpoint is disabled or not yet configured, the ep-\u0026gt;desc\npointer can be NULL. This leads to a NULL pointer dereference when\n__cdns3_gadget_ep_queue() is called, causing a kernel crash.\n\nAdd a check to return -ESHUTDOWN if ep-\u0026gt;desc is NULL, which is the\nstandard return code for unconfigured endpoints.\n\nThis prevents potential crashes when ep_queue is called on endpoints\nthat are not ready.(CVE-2026-31755)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: move wake reason storage into validated event handlers\n\nhci_store_wake_reason() is called from hci_event_packet() immediately\nafter stripping the HCI event header but before hci_event_func()\nenforces the per-event minimum payload length from hci_ev_table.\nThis means a short HCI event frame can reach bacpy() before any bounds\ncheck runs.\n\nRather than duplicating skb parsing and per-event length checks inside\nhci_store_wake_reason(), move wake-address storage into the individual\nevent handlers after their existing event-length validation has\nsucceeded. Convert hci_store_wake_reason() into a small helper that only\nstores an already-validated bdaddr while the caller holds hci_dev_lock().\nUse the same helper after hci_event_func() with a NULL address to\npreserve the existing unexpected-wake fallback semantics when no\nvalidated event handler records a wake address.\n\nAnnotate the helper with __must_hold(\u0026amp;hdev-\u0026gt;lock) and add\nlockdep_assert_held(\u0026amp;hdev-\u0026gt;lock) so future call paths keep the lock\ncontract explicit.\n\nCall the helper from hci_conn_request_evt(), hci_conn_complete_evt(),\nhci_sync_conn_complete_evt(), le_conn_complete_evt(),\nhci_le_adv_report_evt(), hci_le_ext_adv_report_evt(),\nhci_le_direct_adv_report_evt(), hci_le_pa_sync_established_evt(), and\nhci_le_past_received_evt().(CVE-2026-31771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: SMP: derive legacy responder STK authentication from MITM state\n\nThe legacy responder path in smp_random() currently labels the stored\nSTK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH.\nThat reflects what the local service requested, not what the pairing\nflow actually achieved.\n\nFor Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear\nand the resulting STK should remain unauthenticated even if the local\nside requested HIGH security. Use the established MITM state when\nstoring the responder STK so the key metadata matches the pairing result.\n\nThis also keeps the legacy path aligned with the Secure Connections code,\nwhich already treats JUST_WORKS/JUST_CFM as unauthenticated.(CVE-2026-31773)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler()\n\nThe memcpy function assumes the dynamic array notif-\u0026gt;matches is at least\nas large as the number of bytes to copy. Otherwise, results-\u0026gt;matches may\ncontain unwanted data. To guarantee safety, extend the validation in one\nof the checks to ensure sufficient packet length.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2026-31779)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ioc32: stop speculation on the drm_compat_ioctl path\n\nThe drm compat ioctl path takes a user controlled pointer, and then\ndereferences it into a table of function pointers, the signature method\nof spectre problems.  Fix this up by calling array_index_nospec() on the\nindex to the function pointer list.(CVE-2026-31781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: validate LTK enc_size on load\n\nLoad Long Term Keys stores the user-provided enc_size and later uses\nit to size fixed-size stack operations when replying to LE LTK\nrequests. An enc_size larger than the 16-byte key buffer can therefore\noverflow the reply stack buffer.\n\nReject oversized enc_size values while validating the management LTK\nrecord so invalid keys never reach the stored key state.(CVE-2026-43020)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: use skb_header_pointer() for TCPv4 GSO frag_off check\n\nSyzbot reported a KMSAN uninit-value warning in gso_features_check()\ncalled from netif_skb_features() [1].\n\ngso_features_check() reads iph-\u0026gt;frag_off to decide whether to clear\nmangleid_features. Accessing the IPv4 header via ip_hdr()/inner_ip_hdr()\ncan rely on skb header offsets that are not always safe for direct\ndereference on packets injected from PF_PACKET paths.\n\nUse skb_header_pointer() for the TCPv4 frag_off check so the header read\nis robust whether data is already linear or needs copying.\n\n[1] https://syzkaller.appspot.com/bug?extid=1543a7d954d9c6d00407(CVE-2026-43036)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak\n\nWhen processing Router Advertisements with user options the kernel\nbuilds an RTM_NEWNDUSEROPT netlink message. The nduseroptmsg struct\nhas three padding fields that are never zeroed and can leak kernel data\n\nThe fix is simple, just zeroes the padding fields.(CVE-2026-43040)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af-alg - fix NULL pointer dereference in scatterwalk\n\nThe AF_ALG interface fails to unmark the end of a Scatter/Gather List (SGL)\nwhen chaining a new af_alg_tsgl structure. If a sendmsg() fills an SGL\nexactly to MAX_SGL_ENTS, the last entry is marked as the end. A subsequent\nsendmsg() allocates a new SGL and chains it, but fails to clear the end\nmarker on the previous SGL\u0026apos;s last data entry.\n\nThis causes the crypto scatterwalk to hit a premature end, returning NULL\non sg_next() and leading to a kernel panic during dereference.\n\nFix this by explicitly unmarking the end of the previous SGL when\nperforming sg_chain() in af_alg_alloc_tsgl().(CVE-2026-43043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: Fix TX deadlock when using DMA\n\n`dmaengine_terminate_async` does not guarantee that the\n`__dma_tx_complete` callback will run. The callback is currently the\nonly place where `dma-\u0026gt;tx_running` gets cleared. If the transaction is\ncanceled and the callback never runs, then `dma-\u0026gt;tx_running` will never\nget cleared and we will never schedule new TX DMA transactions again.\n\nThis change makes it so we clear `dma-\u0026gt;tx_running` after we terminate\nthe DMA transaction. This is \u0026quot;safe\u0026quot; because `serial8250_tx_dma_flush`\nis holding the UART port lock. The first thing the callback does is also\ngrab the UART port lock, so access to `dma-\u0026gt;tx_running` is serialized.(CVE-2026-43061)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix not releasing workqueue on .release()\n\nThe workqueue associated with an DSA/IAA device is not released when\nthe object is freed.(CVE-2026-43064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Skip discovery table for offline dies\n\nThis warning can be triggered if NUMA is disabled and the system\nboots with fewer CPUs than the number of CPUs in die 0.\n\nWARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]\n\nCurrently, the discovery table continues to be parsed even if all CPUs\nin the associated die are offline.  This can lead to an array overflow\nat \u0026quot;pmu-\u0026gt;boxes[die] = box\u0026quot; in uncore_pci_pmu_register(), which may\ntrigger the warning above or cause other issues.(CVE-2026-43079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: icmp: fix null-ptr-deref in icmp_build_probe()\n\nipv6_stub-\u0026gt;ipv6_dev_find() may return ERR_PTR(-EAFNOSUPPORT) when the\nIPv6 stack is not active (CONFIG_IPV6=m and not loaded), and passing\nthis error pointer to dev_hold() will cause a kernel crash with\nnull-ptr-deref.\n\nInstead, silently discard the request. RFC 8335 does not appear to\ndefine a specific response for the case where an IPv6 interface\nidentifier is syntactically valid but the implementation cannot perform\nthe lookup at runtime, and silently dropping the request may safer than\nmisreporting \u0026quot;No Such Interface\u0026quot;.(CVE-2026-43099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/smp: Add check for kcalloc() failure in parse_thread_groups()\n\nAs kcalloc() may fail, check its return value to avoid a NULL pointer\ndereference when passing it to of_property_read_u32_array().(CVE-2026-43148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: enable basic endpoint checking\n\npegasus_probe() fills URBs with hardcoded endpoint pipes without\nverifying the endpoint descriptors:\n\n  - usb_rcvbulkpipe(dev, 1) for RX data\n  - usb_sndbulkpipe(dev, 2) for TX data\n  - usb_rcvintpipe(dev, 3)  for status interrupts\n\nA malformed USB device can present these endpoints with transfer types\nthat differ from what the driver assumes.\n\nAdd a pegasus_usb_ep enum for endpoint numbers, replacing magic\nconstants throughout. Add usb_check_bulk_endpoints() and\nusb_check_int_endpoints() calls before any resource allocation to\nverify endpoint types before use, rejecting devices with mismatched\ndescriptors at probe time, and avoid triggering assertion.\n\nSimilar fix to\n- commit 90b7f2961798 (\u0026quot;net: usb: rtl8150: enable basic endpoint checking\u0026quot;)\n- commit 9e7021d2aeae (\u0026quot;net: usb: catc: enable basic endpoint checking\u0026quot;)(CVE-2026-43156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/bitmap: fix GPF in write_page caused by resize race\n\nA General Protection Fault occurs in write_page() during array resize:\nRIP: 0010:write_page+0x22b/0x3c0 [md_mod]\n\nThis is a use-after-free race between bitmap_daemon_work() and\n__bitmap_resize(). The daemon iterates over `bitmap-\u0026gt;storage.filemap`\nwithout locking, while the resize path frees that storage via\nmd_bitmap_file_unmap(). `quiesce()` does not stop the md thread,\nallowing concurrent access to freed pages.\n\nFix by holding `mddev-\u0026gt;bitmap_info.mutex` during the bitmap update.(CVE-2026-43163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data()\n\nOn the receive path, __ioam6_fill_trace_data() uses trace-\u0026gt;nodelen\nto decide how much data to write for each node. It trusts this field\nas-is from the incoming packet, with no consistency check against\ntrace-\u0026gt;type (the 24-bit field that tells which data items are\npresent). A crafted packet can set nodelen=0 while setting type bits\n0-21, causing the function to write ~100 bytes past the allocated\nregion (into skb_shared_info), which corrupts adjacent heap memory\nand leads to a kernel panic.\n\nAdd a shared helper ioam6_trace_compute_nodelen() in ioam6.c to\nderive the expected nodelen from the type field, and use it:\n\n  - in ioam6_iptunnel.c (send path, existing validation) to replace\n    the open-coded computation;\n  - in exthdrs.c (receive path, ipv6_hop_ioam) to drop packets whose\n    nodelen is inconsistent with the type field, before any data is\n    written.\n\nPer RFC 9197, bits 12-21 are each short (4-octet) fields, so they\nare included in IOAM6_MASK_SHORT_FIELDS (changed from 0xff100000 to\n0xff1ffc00).(CVE-2026-43186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE\n\nThe arch definition of cpumask_of_node() cannot handle NUMA_NO_NODE -\nwhich is a valid index - so add a check for this.(CVE-2026-43212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/kexec: add a sanity check on previous kernel\u0026apos;s ima kexec buffer\n\nWhen the second-stage kernel is booted via kexec with a limiting command\nline such as \u0026quot;mem=\u0026lt;size\u0026gt;\u0026quot;, the physical range that contains the carried\nover IMA measurement list may fall outside the truncated RAM leading to a\nkernel panic.\n\n    BUG: unable to handle page fault for address: ffff97793ff47000\n    RIP: ima_restore_measurement_list+0xdc/0x45a\n    #PF: error_code(0x0000) – not-present page\n\nOther architectures already validate the range with page_is_ram(), as done\nin commit cbf9c4b9617b (\u0026quot;of: check previous kernel\u0026apos;s ima-kexec-buffer\nagainst memory bounds\u0026quot;) do a similar check on x86.\n\nWithout carrying the measurement list across kexec, the attestation\nwould fail.(CVE-2026-43240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fiemap page fault fix\n\nIn gfs2_fiemap(), we are calling iomap_fiemap() while holding the inode\nglock.  This can lead to recursive glock taking if the fiemap buffer is\nmemory mapped to the same inode and accessing it triggers a page fault.\n\nFix by disabling page faults for iomap_fiemap() and faulting in the\nbuffer by hand if necessary.\n\nFixes xfstest generic/742.(CVE-2026-43262)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: supply snapshot context in ceph_zero_partial_object()\n\nThe ceph_zero_partial_object function was missing proper snapshot\ncontext for its OSD write operations, which could lead to data\ninconsistencies in snapshots.\n\nReproducer:\n../src/vstart.sh --new -x --localhost --bluestore\n./bin/ceph auth caps client.fs_a mds \u0026apos;allow rwps fsname=a\u0026apos; mon \u0026apos;allow r fsname=a\u0026apos; osd \u0026apos;allow rw tag cephfs data=a\u0026apos;\nmount -t ceph (CVE-2026-43273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: move ext4_percpu_param_init() before ext4_mb_init()\n\nWhen running `kvm-xfstests -c ext4/1k -C 1 generic/383` with the\n`DOUBLE_CHECK` macro defined, the following panic is triggered:\n\n==================================================================\nEXT4-fs error (device vdc): ext4_validate_block_bitmap:423:\n                        comm mount: bg 0: bad block bitmap checksum\nBUG: unable to handle page fault for address: ff110000fa2cc000\nPGD 3e01067 P4D 3e02067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W\n                        6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none)\nRIP: 0010:percpu_counter_add_batch+0x13/0xa0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_mark_group_bitmap_corrupted+0xcb/0xe0\n ext4_validate_block_bitmap+0x2a1/0x2f0\n ext4_read_block_bitmap+0x33/0x50\n mb_group_bb_bitmap_alloc+0x33/0x80\n ext4_mb_add_groupinfo+0x190/0x250\n ext4_mb_init_backend+0x87/0x290\n ext4_mb_init+0x456/0x640\n __ext4_fill_super+0x1072/0x1680\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n vfs_cmd_create+0x59/0xe0\n __do_sys_fsconfig+0x4f6/0x6b0\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nThis issue can be reproduced using the following commands:\n        mkfs.ext4 -F -q -b 1024 /dev/sda 5G\n        tune2fs -O quota,project /dev/sda\n        mount /dev/sda /tmp/test\n\nWith DOUBLE_CHECK defined, mb_group_bb_bitmap_alloc() reads\nand validates the block bitmap. When the validation fails,\next4_mark_group_bitmap_corrupted() attempts to update\nsbi-\u0026gt;s_freeclusters_counter. However, this percpu_counter has not been\ninitialized yet at this point, which leads to the panic described above.\n\nFix this by moving the execution of ext4_percpu_param_init() to occur\nbefore ext4_mb_init(), ensuring the per-CPU counters are initialized\nbefore they are used.(CVE-2026-43288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node\n\nWhen CONFIG_PAGE_OWNER is enabled, freeing KASAN shadow pages during\nvmalloc cleanup triggers expensive stack unwinding that acquires RCU read\nlocks.  Processing a large purge_list without rescheduling can cause the\ntask to hold CPU for extended periods (10+ seconds), leading to RCU stalls\nand potential OOM conditions.\n\nThe issue manifests in purge_vmap_node() -\u0026gt; kasan_release_vmalloc_node()\nwhere iterating through hundreds or thousands of vmap_area entries and\nfreeing their associated shadow pages causes:\n\n  rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:\n  rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P6229/1:b..l\n  ...\n  task:kworker/0:17 state:R running task stack:28840 pid:6229\n  ...\n  kasan_release_vmalloc_node+0x1ba/0xad0 mm/vmalloc.c:2299\n  purge_vmap_node+0x1ba/0xad0 mm/vmalloc.c:2299\n\nEach call to kasan_release_vmalloc() can free many pages, and with\npage_owner tracking, each free triggers save_stack() which performs stack\nunwinding under RCU read lock.  Without yielding, this creates an\nunbounded RCU critical section.\n\nAdd periodic cond_resched() calls within the loop to allow:\n- RCU grace periods to complete\n- Other tasks to run\n- Scheduler to preempt when needed\n\nThe fix uses need_resched() for immediate response under load, with a\nbatch count of 32 as a guaranteed upper bound to prevent worst-case stalls\neven under light load.(CVE-2026-43292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipa: fix event ring index not programmed for IPA v5.0+\n\nFor IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to\nCH_C_CNTXT_1. The v5.0 register definition intended to define this\nfield in the CH_C_CNTXT_1 fmask array but used the old identifier of\nERINDEX instead of CH_ERINDEX.\n\nWithout a valid event ring, GSI channels could never signal transfer\ncompletions. This caused gsi_channel_trans_quiesce() to block\nforever in wait_for_completion().\n\nAt least for IPA v5.2 this resolves an issue seen where runtime\nsuspend, system suspend, and remoteproc stop all hanged forever. It\nalso meant the IPA data path was completely non functional.(CVE-2026-43345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/kbuf: check if target buffer list is still legacy on recycle\n\nThere\u0026apos;s a gap between when the buffer was grabbed and when it\npotentially gets recycled, where if the list is empty, someone could\u0026apos;ve\nupgraded it to a ring provided type. This can happen if the request\nis forced via io-wq. The legacy recycling is missing checking if the\nbuffer_list still exists, and if it\u0026apos;s of the correct type. Add those\nchecks.(CVE-2026-43366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in process_message_header()\n\nIf the message frame is (maliciously) corrupted in a way that the\nlength of the control segment ends up being less than the size of the\nmessage header or a different frame is made to look like a message\nframe, out-of-bounds reads may ensue in process_message_header().\n\nPerform an explicit bounds check before decoding the message header.(CVE-2026-43406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix memory leaks in ceph_mdsc_build_path()\n\nAdd __putname() calls to error code paths that did not free the \u0026quot;path\u0026quot;\npointer obtained by __getname().  If ownership of this pointer is not\npassed to the caller via path_info.path, the function must free it\nbefore returning.(CVE-2026-43419)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: class: cdc-wdm: fix reordering issue in read code path\n\nQuoting the bug report:\n\nDue to compiler optimization or CPU out-of-order execution, the\ndesc-\u0026gt;length update can be reordered before the memmove. If this\nhappens, wdm_read() can see the new length and call copy_to_user() on\nuninitialized memory. This also violates LKMM data race rules [1].\n\nFix it by using WRITE_ONCE and memory barriers.(CVE-2026-43427)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Limit the length of unkillable synchronous timeouts\n\nThe usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in\nusbcore allow unlimited timeout durations.  And since they use\nuninterruptible waits, this leaves open the possibility of hanging a\ntask for an indefinitely long time, with no way to kill it short of\nunplugging the target device.\n\nTo prevent this sort of problem, enforce a maximum limit on the length\nof these unkillable timeouts.  The limit chosen here, somewhat\narbitrarily, is 60 seconds.  On many systems (although not all) this\nis short enough to avoid triggering the kernel\u0026apos;s hung-task detector.\n\nIn addition, clear up the ambiguity of negative timeout values by\ntreating them the same as 0, i.e., using the maximum allowed timeout.(CVE-2026-43428)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix deadlock between devlink lock and esw-\u0026gt;wq\n\nesw-\u0026gt;work_queue executes esw_functions_changed_event_handler -\u0026gt;\nesw_vfs_changed_event_handler and acquires the devlink lock.\n\n.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -\u0026gt;\nmlx5_devlink_eswitch_mode_set -\u0026gt; mlx5_eswitch_disable_locked -\u0026gt;\nmlx5_eswitch_event_handler_unregister -\u0026gt; flush_workqueue deadlocks\nwhen esw_vfs_changed_event_handler executes.\n\nFix that by no longer flushing the work to avoid the deadlock, and using\na generation counter to keep track of work relevance. This avoids an old\nhandler manipulating an esw that has undergone one or more mode changes:\n- the counter is incremented in mlx5_eswitch_event_handler_unregister.\n- the counter is read and passed to the ephemeral mlx5_host_work struct.\n- the work handler takes the devlink lock and bails out if the current\n  generation is different than the one it was scheduled to operate on.\n- mlx5_eswitch_cleanup does the final draining before destroying the wq.\n\nNo longer flushing the workqueue has the side effect of maybe no longer\ncancelling pending vport_change_handler work items, but that\u0026apos;s ok since\nthose are disabled elsewhere:\n- mlx5_eswitch_disable_locked disables the vport eq notifier.\n- mlx5_esw_vport_disable disarms the HW EQ notification and marks\n  vport-\u0026gt;enabled under state_lock to false to prevent pending vport\n  handler from doing anything.\n- mlx5_eswitch_cleanup destroys the workqueue and makes sure all events\n  are disabled/finished.(CVE-2026-43468)\n\nIn the Linux kernel, the following vulnerability has been resolved:  crypto: pcrypt - Fix handling of MAY_BACKLOG requests  MAY_BACKLOG requests can return EBUSY.  Handle them by checking for that value and filtering out EINPROGRESS notifications.  The Linux kernel CVE team has assigned CVE-2026-43493 to this issue.(CVE-2026-43493)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skbuff: propagate shared-frag marker through frag-transfer helpers\n\nTwo frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail\nto propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()-\u0026gt;flags when\nmoving frags from source to destination.  __pskb_copy_fclone() defers\nthe rest of the shinfo metadata to skb_copy_header() after copying\nfrag descriptors, but that helper only carries over gso_{size,segs,\ntype} and never touches skb_shinfo()-\u0026gt;flags; skb_shift() moves frag\ndescriptors directly and leaves flags untouched.  As a result, the\ndestination skb keeps a reference to the same externally-owned or\npage-cache-backed pages while reporting skb_has_shared_frag() as\nfalse.\n\nThe mismatch is harmful in any in-place writer that uses\nskb_has_shared_frag() to decide whether shared pages must be detoured\nthrough skb_cow_data().  ESP input is one such writer (esp4.c,\nesp6.c), and a single nft \u0026apos;dup to \u0026lt;local\u0026gt;\u0026apos; rule -- or any other\nnf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()\u0026apos;d\nskb in esp_input() with the marker stripped, letting an unprivileged\nuser write into the page cache of a root-owned read-only file via\nauthencesn-ESN stray writes.\n\nSet SKBFL_SHARED_FRAG on the destination whenever frag descriptors\nwere actually moved from the source.  skb_copy() and skb_copy_expand()\nshare skb_copy_header() too but linearize all paged data into freshly\nallocated head storage and emerge with nr_frags == 0, so\nskb_has_shared_frag() returns false on its own; they need no change.\n\nThe same omission exists in skb_gro_receive() and skb_gro_receive_list().\nThe former moves the incoming skb\u0026apos;s frag descriptors into the\naccumulator\u0026apos;s last sub-skb via two paths (a direct frag-move loop and\nthe head_frag + memcpy path); the latter chains the incoming skb whole\nonto p\u0026apos;s frag_list.  Downstream skb_segment() reads only\nskb_shinfo(p)-\u0026gt;flags, and skb_segment_list() reuses each sub-skb\u0026apos;s\nshinfo as the nskb -- both p and lp must carry the marker.\n\nThe same omission also exists in tcp_clone_payload(), which builds an\nMTU probe skb by moving frag descriptors from skbs on sk_write_queue\ninto a freshly allocated nskb.  The helper falls into the same family\nand warrants the same fix for consistency; no TCP TX-side in-place\nwriter is currently known to reach a user page through this gap, but\na future consumer depending on the marker would regress silently.\n\nThe same omission exists in skb_segment(): the per-iteration flag\nmerge takes only head_skb\u0026apos;s flag, and the inner switch that rebinds\nfrag_skb to list_skb on head_skb-frags exhaustion does not fold the\nnew frag_skb\u0026apos;s flag into nskb.  Fold frag_skb\u0026apos;s flag at both sites\nso segments drawing frags from frag_list members carry the marker.(CVE-2026-43503)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb()\n\nAdd the same NULL guard already present in\nl2cap_sock_resume_cb() and l2cap_sock_ready_cb().(CVE-2026-45834)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix slab-use-after-free in qd_put\n\nCommit a475c5dd16e5 (\u0026quot;gfs2: Free quota data objects synchronously\u0026quot;)\nstarted freeing quota data objects during filesystem shutdown instead of\nputting them back onto the LRU list, but it failed to remove these\nobjects from the LRU list, causing LRU list corruption.  This caused\nuse-after-free when the shrinker (gfs2_qd_shrink_scan) tried to access\nalready-freed objects on the LRU list.\n\nFix this by removing qd objects from the LRU list before freeing them in\nqd_put().\n\nInitial fix from Deepanshu Kartikey \u0026lt;(CVE-2026-45861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix role switching during resume\n\nIf the role change while we are suspended, the cdns3 driver switches to the\nnew mode during resume. However, switching to host mode in this context\ncauses a NULL pointer dereference.\n\nThe host role\u0026apos;s start() operation registers a xhci-hcd device, but its\nprobe is deferred while we are in the resume path. The host role\u0026apos;s resume()\noperation assumes the xhci-hcd device is already probed, which is not the\ncase, leading to the dereference. Since the start() operation of the new\nrole is already called, the resume operation can be skipped.\n\nSo skip the resume operation for the new role if a role switch occurs\nduring resume. Once the resume sequence is complete, the xhci-hcd device\ncan be probed in case of host mode.\n\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000208\nMem abort info:\n...\nData abort info:\n...\n[0000000000000208] pgd=0000000000000000, p4d=0000000000000000\nInternal error: Oops: 0000000096000004 [#1]  SMP\nModules linked in:\nCPU: 0 UID: 0 PID: 146 Comm: sh Not tainted\n6.19.0-rc7-00013-g6e64f4aabfae-dirty #135 PREEMPT\nHardware name: Texas Instruments J7200 EVM (DT)\npstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : usb_hcd_is_primary_hcd+0x0/0x1c\nlr : cdns_host_resume+0x24/0x5c\n...\nCall trace:\n usb_hcd_is_primary_hcd+0x0/0x1c (P)\n cdns_resume+0x6c/0xbc\n cdns3_controller_resume.isra.0+0xe8/0x17c\n cdns3_plat_resume+0x18/0x24\n platform_pm_resume+0x2c/0x68\n dpm_run_callback+0x90/0x248\n device_resume+0x100/0x24c\n dpm_resume+0x190/0x2ec\n dpm_resume_end+0x18/0x34\n suspend_devices_and_enter+0x2b0/0xa44\n pm_suspend+0x16c/0x5fc\n state_store+0x80/0xec\n kobj_attr_store+0x18/0x2c\n sysfs_kf_write+0x7c/0x94\n kernfs_fop_write_iter+0x130/0x1dc\n vfs_write+0x240/0x370\n ksys_write+0x70/0x108\n __arm64_sys_write+0x1c/0x28\n invoke_syscall+0x48/0x10c\n el0_svc_common.constprop.0+0x40/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x34/0x108\n el0t_64_sync_handler+0xa0/0xe4\n el0t_64_sync+0x198/0x19c\nCode: 52800003 f9407ca5 d63f00a0 17ffffe4 (f9410401)\n---[ end trace 0000000000000000 ]---(CVE-2026-45911)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix inline data read failure for ztailpacking pclusters\n\nCompressed folios for ztailpacking pclusters must be valid before adding\nthese pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster()\nmay assume they are already valid and then trigger a NULL pointer\ndereference.\n\nIt is somewhat hard to reproduce because the inline data is in the same\nblock as the tail of the compressed indexes, which are usually read just\nbefore. However, it may still happen if a fatal signal arrives while\nread_mapping_folio() is running, as shown below:\n\n erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008\n\n ...\n\n pc : z_erofs_decompress_queue+0x4c8/0xa14\n lr : z_erofs_decompress_queue+0x160/0xa14\n sp : ffffffc08b3eb3a0\n x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000\n x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001\n x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700\n x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098\n x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004\n x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9\n x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000\n x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000000000003f\n x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020\n x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n  z_erofs_decompress_queue+0x4c8/0xa14\n  z_erofs_runqueue+0x908/0x97c\n  z_erofs_read_folio+0x128/0x228\n  filemap_read_folio+0x68/0x128\n  filemap_get_pages+0x44c/0x8b4\n  filemap_read+0x12c/0x5b8\n  generic_file_read_iter+0x4c/0x15c\n  do_iter_readv_writev+0x188/0x1e0\n  vfs_iter_read+0xac/0x1a4\n  backing_file_read_iter+0x170/0x34c\n  ovl_read_iter+0xf0/0x140\n  vfs_read+0x28c/0x344\n  ksys_read+0x80/0xf0\n  __arm64_sys_read+0x24/0x34\n  invoke_syscall+0x60/0x114\n  el0_svc_common+0x88/0xe4\n  do_el0_svc+0x24/0x30\n  el0_svc+0x40/0xa8\n  el0t_64_sync_handler+0x70/0xbc\n  el0t_64_sync+0x1bc/0x1c0\n\nFix this by reading the inline data before allocating and adding\nthe pclusters to the I/O chains.(CVE-2026-45943)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc()\n\nIn amdgpu_acpi_enumerate_xcc(), if amdgpu_acpi_dev_init() returns -ENOMEM,\nthe function returns directly without releasing the allocated xcc_info,\nresulting in a memory leak.\n\nFix this by ensuring that xcc_info is properly freed in the error paths.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-45947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fix memory leaks in gfs2_fill_super error path\n\nFix two memory leaks in the gfs2_fill_super() error handling path when\ntransitioning a filesystem to read-write mode fails.\n\nFirst leak: kthread objects (thread_struct, task_struct, etc.)\nWhen gfs2_freeze_lock_shared() fails after init_threads() succeeds, the\ncreated kernel threads (logd and quotad) are never destroyed. This\noccurs because the fail_per_node label doesn\u0026apos;t call\ngfs2_destroy_threads().\n\nSecond leak: quota bitmap buffer (8192 bytes)\nWhen gfs2_make_fs_rw() fails after gfs2_quota_init() succeeds but\nbefore other operations complete, the allocated quota bitmap is never\nfreed.\n\nThe fix moves thread cleanup to the fail_per_node label to handle all\nerror paths uniformly. gfs2_destroy_threads() is safe to call\nunconditionally as it checks for NULL pointers. Quota cleanup is added\nin gfs2_make_fs_rw() to properly handle the withdrawal case where\nquota initialization succeeds but the filesystem is then withdrawn.\n\nThread leak backtrace (gfs2_freeze_lock_shared failure):\n  unreferenced object 0xffff88801d7bca80 (size 4480):\n    copy_process+0x3a1/0x4670 kernel/fork.c:2422\n    kernel_clone+0xf3/0x6e0 kernel/fork.c:2779\n    kthread_create_on_node+0x100/0x150 kernel/kthread.c:478\n    init_threads+0xab/0x350 fs/gfs2/ops_fstype.c:611\n    gfs2_fill_super+0xe5c/0x1240 fs/gfs2/ops_fstype.c:1265\n\nQuota leak backtrace (gfs2_make_fs_rw failure):\n  unreferenced object 0xffff88812de7c000 (size 8192):\n    gfs2_quota_init+0xe5/0x820 fs/gfs2/quota.c:1409\n    gfs2_make_fs_rw+0x7a/0xe0 fs/gfs2/super.c:149\n    gfs2_fill_super+0xfbb/0x1240 fs/gfs2/ops_fstype.c:1275(CVE-2026-45961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch()\n\nCover a missed execution path with a new check.(CVE-2026-45982)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix unsigned underflow in z_erofs_lz4_handle_overlap()\n\nSome crafted images can have illegal (!partial_decoding \u0026amp;\u0026amp;\nm_llen \u0026lt; m_plen) extents, and the LZ4 inplace decompression path\ncan be wrongly hit, but it cannot handle (outpages \u0026lt; inpages)\nproperly: \u0026quot;outpages - inpages\u0026quot; wraps to a large value and\nthe subsequent rq-\u0026gt;out[] access reads past the decompressed_pages\narray.\n\nHowever, such crafted cases can correctly result in a corruption\nreport in the normal LZ4 non-inplace path.\n\nLet\u0026apos;s add an additional check to fix this for backporting.\n\nReproducible image (base64-encoded gzipped blob):\n\nH4sIAJGR12kCA+3SPUoDQRgG4MkmkkZk8QRbRFIIi9hbpEjrHQI5ghfwCN5BLCzTGtLbBI+g\ndilSJo1CnIm7GEXFxhT6PDDwfrs73/ywIQD/1ePD4r7Ou6ETsrq4mu7XcWfj++Pb58nJU/9i\nPNtbjhan04/9GtX4qVYc814WDqt6FaX5s+ZwXXeq52lndT6IuVvlblytLMvh4Gzwaf90nsvz\n2DF/21+20T/ldgp5s1jXRaN4t/8izsy/OUB6e/Qa79r+JwAAAAAAAL52vQVuGQAAAP6+my1w\nywAAAAAAAADwu14ATsEYtgBQAAA=\n\n$ mount -t erofs -o cache_strategy=disabled foo.erofs /mnt\n$ dd if=/mnt/data of=/dev/null bs=4096 count=1(CVE-2026-45999)\n\nIn the Linux kernel, the following vulnerability has been resolved:  ipmi:ssif: Clean up kthread on errors  If an error occurs after the ssif kthread is created, but before the main IPMI code starts the ssif interface, the ssif kthread will not be stopped.  So make sure the kthread is stopped on an error condition if it is running.  The Linux kernel CVE team has assigned CVE-2026-46044 to this issue.(CVE-2026-46044)\n\nIn the Linux kernel, the following vulnerability has been resolved:  md/raid5: fix soft lockup in retry_aligned_read()  When retry_aligned_read() encounters an overlapped stripe, it releases the stripe via raid5_release_stripe() which puts it on the lockless released_stripes llist. In the next raid5d loop iteration, release_stripe_list() drains the stripe onto handle_list (since STRIPE_HANDLE is set by the original IO), but retry_aligned_read() runs before handle_active_stripes() and removes the stripe from handle_list via find_get_stripe() -\u0026gt; list_del_init(). This prevents handle_stripe() from ever processing the stripe to resolve the overlap, causing an infinite loop and soft lockup.  Fix this by using __release_stripe() with temp_inactive_list instead of raid5_release_stripe() in the failure path, so the stripe does not go through the released_stripes llist. This allows raid5d to break out of its loop, and the overlap will be resolved when the stripe is eventually processed by handle_stripe().  The Linux kernel CVE team has assigned CVE-2026-46051 to this issue.(CVE-2026-46051)\n\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: nSVM: Raise #UD if unhandled VMMCALL isn\u0026apos;t intercepted by L1  Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1.  The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it\u0026apos;s not intercepted.  Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses.  The last remaining \u0026quot;single\u0026quot; stub will soon be dropped as well.  [sean: rewrite changelog and comment, tag for stable, remove defunct stubs]  The Linux kernel CVE team has assigned CVE-2026-46076 to this issue.(CVE-2026-46076)\n\nIn the Linux kernel, the following vulnerability has been resolved:  erofs: fix the out-of-bounds nameoff handling for trailing dirents  Currently we already have boundary-checks for nameoffs, but the trailing dirents are special since the namelens are calculated with strnlen() with unchecked nameoffs.  If a crafted EROFS has a trailing dirent with nameoff \u0026gt;= maxsize, maxsize - nameoff can underflow, causing strnlen() to read past the directory block.  nameoff0 should also be verified to be a multiple of `sizeof(struct erofs_dirent)` as well [1].  [1] https://sashiko.dev/#/patchset/20260416063511.3173774-1-hsiangkao%40linux.alibaba.com  The Linux kernel CVE team has assigned CVE-2026-46078 to this issue.(CVE-2026-46078)\n\nIn the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0  INVLPGA should cause a #UD when EFER.SVME is not set. Add a check to properly inject #UD when EFER.SVME=0.  [sean: tag for stable@]  The Linux kernel CVE team has assigned CVE-2026-46082 to this issue.(CVE-2026-46082)\n\nIn the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: take vmap_purge_lock in shrinker  decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan().  However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks.  Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users.  The Linux kernel CVE team has assigned CVE-2026-46093 to this issue.(CVE-2026-46093)\n\nIn the Linux kernel, the following vulnerability has been resolved:mm/damon/sysfs-schemes: protect memcg_path kfree() with damon_sysfs_lockPatch series \u0026quot;mm/damon/sysfs-schemes: fix use-after-free for [memcg_]path\u0026quot;.Reads of \u0026apos;memcg_path\u0026apos; and \u0026apos;path\u0026apos; files in DAMON sysfs interface could racewith their writes, results in use-after-free.  Fix those.This patch (of 2):damon_sysfs_scheme_filter-\u0026gt;mmecg_path can be read and written by users,via DAMON sysfs memcg_path file.  It can also be indirectly read, for theparameters {on,off}line committing to DAMON.  The reads for parameterscommitting are protected by damon_sysfs_lock to avoid the sysfs filesbeing destroyed while any of the parameters are being read.  But theuser-driven direct reads and writes are not protected by any lock, whilethe write is deallocating the memcg_path-pointing buffer.  As a result,the readers could read the already freed buffer (user-after-free).  Notethat the user-reads don\u0026apos;t race when the same open file is used by thewriter, due to kernfs\u0026apos;s open file locking.  Nonetheless, doing the readsand writes with separate open files would be common.  Fix it by protectingboth the user-direct reads and writes with damon_sysfs_lock.(CVE-2026-46121)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt\n\nhci_le_create_big_complete_evt() iterates over BT_BOUND connections for\na BIG handle using a while loop, accessing ev-\u0026gt;bis_handle[i++] on each\niteration.  However, there is no check that i stays within ev-\u0026gt;num_bis\nbefore the array access.\n\nWhen a controller sends a LE_Create_BIG_Complete event with fewer\nbis_handle entries than there are BT_BOUND connections for that BIG,\nor with num_bis=0, the loop reads beyond the valid bis_handle[] flex\narray into adjacent heap memory.  Since the out-of-bounds values\ntypically exceed HCI_CONN_HANDLE_MAX (0x0EFF), hci_conn_set_handle()\nrejects them and the connection remains in BT_BOUND state.  The same\nconnection is then found again by hci_conn_hash_lookup_big_state(),\ncreating an infinite loop with hci_dev_lock held.\n\nFix this by terminating the BIG if in case not all BIS could be setup\nproperly.(CVE-2026-46138)\n\nIn the Linux kernel, vports are used concurrently and protected by RCU, so netdev_put() must happen after the RCU grace period. The rtnl_delete_link() must happen under RTNL and cannot be executed in RCU context. Calling synchronize_net() while holding RTNL is not good for performance and system stability, so calling netdev_put() in RCU call is the right solution. However, when the device is deleted, rtnl_unlock() calls netdev_run_todo() and blocks until all references are gone. In the current code, this means that call_rcu() is never reached, the vport is never freed, and the reference is never released, causing a self-deadlock on device removal. The fix moves the rcu_call() before rtnl_unlock(), so the scheduled RCU callback will be executed when synchronize_net() is called from rtnl_unlock()-\u0026gt;netdev_run_todo() while RTNL itself is already released.(CVE-2026-46165)\n\nIn the Linux kernel\u0026apos;s RISC-V KVM subsystem, when the second kzalloc (host_context.vector.datap) fails in kvm_riscv_vcpu_alloc_vector_context, the first allocation (guest_context.vector.datap) is not freed, causing a memory leak. An attacker can trigger this via ioctl(vm_fd, KVM_CREATE_VCPU), potentially leading to resource exhaustion.(CVE-2026-46171)\n\nIn the Linux kernel, the mlx4_ib_create_srq() function fails to release resources allocated by mlx4_srq_alloc() in error handling paths, leading to a resource leak. An attacker could exploit this vulnerability to cause resource exhaustion or denial of service.(CVE-2026-46178)\n\nIn the Linux kernel, the spi_nor_params_show() function uses sizeof(snor_f_names) to calculate the array length. Since snor_f_names is an array of pointers, sizeof returns the total byte size of the pointer array (element_count  sizeof(void )), which on 64-bit systems is 8 times larger than intended. This causes an out-of-bounds read when a flag bit is set that exceeds the actual element count but falls within the inflated byte-size count. The fix replaces sizeof with ARRAY_SIZE to pass the actual number of elements.(CVE-2026-46190)","status":"published","published":"2026-06-05T11:11:31Z","modified":"2026-08-18T01:20:04.171596141Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2026-23138","title":"CVE-2026-23138 in linux - Patched by Root","description":"Root has patched CVE-2026-23138 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:18:14.653139196Z","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.900552Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2026-23138","title":"CVE-2026-23138 in linux - Patched by Root","description":"Root has patched CVE-2026-23138 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:15:48.597840916Z","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-2204-CVE-2026-23138","title":"CVE-2026-23138 in linux - Patched by Root","description":"Root has patched CVE-2026-23138 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:17:22.012375853Z","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-06T14:57:22.237547Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23138","title":"CVE-2026-23138 in linux - Patched by Root","description":"Root has patched CVE-2026-23138 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:18:04.325219891Z","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:59:13.602872Z"},{"id":"UBUNTU-CVE-2026-23138","description":"In the Linux kernel, the following vulnerability has been resolved: tracing: Add recursion protection in kernel stack trace recording A bug was reported about an infinite recursion caused by tracing the rcu events with the kernel stack trace trigger enabled. The stack trace code called back into RCU which then called the stack trace again. Expand the ftrace recursion protection to add a set of bits to protect events from recursion. Each bit represents the context that the event is in (normal, softirq, interrupt and NMI). Have the stack trace code use the interrupt context to protect against recursion. Note, the bug showed an issue in both the RCU code as well as the tracing stacktrace code. This only handles the tracing stack trace side of the bug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T16:15:00Z","modified":"2026-11-10T02:49:49.832985227Z","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-10T03:19:00.855684Z"},{"id":"AZL-77703","title":"CVE-2026-23138 affecting package kernel for versions less than 6.6.130.1-3","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T16:15:53Z","modified":"2026-11-05T05:40:51Z","updated_at":"2026-11-05T16:41:24.626116Z"},{"id":"CLSA-2026-1782155469","title":"kernel: Fix of 143 CVEs","description":"- ice: Fix PTP NULL pointer dereference during VSI rebuild {CVE-2026-23210}\n- tracing: Add recursion protection in kernel stack trace recording {CVE-2026-23138}\n- mm/ptdump: take the memory hotplug lock inside ptdump_walk_pgd() {CVE-2025-38681}\n- cpuset: fix warning when disabling remote partition {CVE-2025-71142}\n- virtio: break and reset virtio devices on device_shutdown() {CVE-2025-38064}\n- netdevsim: fix a race issue related to the operation on bpf_bound_progs list {CVE-2026-23126}\n- atm: clip: Fix potential null-ptr-deref in to_atmarpd(). {CVE-2025-38460}\n- idpf: fix error handling in the init_task on load {CVE-2026-23017}\n- rxrpc: Fix recvmsg() unconditional requeue {CVE-2026-23066}\n- block: zero non-PI portion of auto integrity buffer {CVE-2026-23007}\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode {CVE-2025-38665}\n- virtio_net: Fix napi_skb_cache_put warning {CVE-2024-43835}\n- crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg {CVE-2025-39964}\n- mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() {CVE-2026-23169}\n- net: fix segmentation of forwarding fraglist GRO {CVE-2026-23154}\n- gfs2: Validate i_depth for exhash directories {CVE-2025-38710}\n- KVM: Don't clobber irqfd routing type when deassigning irqfd {CVE-2026-23198}\n- ipvlan: Make the addrs_lock be per port {CVE-2026-23103}\n- xfs: fix freemap adjustments when adding xattrs to leaf blocks {CVE-2026-43158}\n- can: mcp251xfd: fix infinite loop when xmit fails {CVE-2024-41088}\n- RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly {CVE-2025-71096}\n- RDMA/mlx5: Fix error flow upon firmware failure for RQ destruction {CVE-2025-38161}\n- scsi: qla2xxx: Validate sp before freeing associated memory {CVE-2025-71236}\n- net/sched: netem: account for backlog updates from child qdisc {CVE-2024-56770}\n- drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat {CVE-2026-31656}\n- iavf: fix off-by-one issues in iavf_config_rss_reg() {CVE-2025-71087}\n- net/sched: ets: fix divide by zero in the offload path {CVE-2026-23379}\n- can: j1939: implement NETDEV_UNREGISTER notification handler {CVE-2025-39925}\n- ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() {CVE-2026-31531}\n- Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb {CVE-2026-31510}\n- ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() {CVE-2026-23003}\n- drm/i915/gt: Check set_default_submission() before deferencing {CVE-2026-31540}\n- mac802154: check local interfaces before deleting sdata list {CVE-2024-57948}\n- lib/buildid: use __kernel_read() for sleepable context {CVE-2026-23002}\n- scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs {CVE-2023-52808}\n- net: fix memory leak in skb_segment_list for GRO packets {CVE-2026-22979}\n- irqchip/imx-irqsteer: Handle runtime power management correctly {CVE-2024-42290}\n- io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop {CVE-2026-23113}\n- net/sched: ets: Remove drr class from the active list if it changes to strict {CVE-2025-68815}\n- net: bonding: fix NULL deref in bond_debug_rlb_hash_show {CVE-2026-31546}\n- ipvs: fix ipv4 null-ptr-deref in route error path {CVE-2025-68813}\n- openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}\n- net: USB: Fix wrong-direction WARNING in plusb.c {CVE-2023-52742}\n- module: Fix kernel panic when a symbol st_shndx is out of bounds {CVE-2026-31521}\n- udf: Fix preallocation discarding at indirect extent boundary {CVE-2022-48946}\n- net/mlx5: qos: Restrict RTNL area to avoid a lock cycle {CVE-2025-39947}\n- scsi: core: Wake up the error handler when final completions race against each other {CVE-2026-23110}\n- nbd: don't allow reconnect after disconnect {CVE-2025-21731}\n- nfsd: check that server is running in unlock_filesystem {CVE-2026-22989}\n- af_key: validate families in pfkey_send_migrate() {CVE-2026-31515}\n- netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() {CVE-2024-36286}\n- scsi: qla2xxx: Delay module unload while fabric scan in progress {CVE-2025-71235}\n- smc91x: fix broken irq-context in PREEMPT_RT {CVE-2025-71132}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- net: stmmac: fix the crash issue for zero copy XDP_TX action {CVE-2025-71095}\n- kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case {CVE-2022-49779}\n- wifi: ath11k: add srng-\u003elock for ath11k_hal_srng_* in monitor mode {CVE-2024-58096}\n- Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop {CVE-2026-31498}\n- ipv4: Fix reference count leak when using error routes with nexthop objects {CVE-2025-71097}\n- idpf: fix null-ptr-deref in idpf_features_check {CVE-2025-38053}\n- net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled {CVE-2026-23381}\n- xen/privcmd: fix error exit of privcmd_ioctl_dm_op() {CVE-2022-49989}\n- crypto: null - Use spin lock instead of mutex {CVE-2025-37808}\n- x86/efistub: Call mixed mode boot services on the firmware's stack {CVE-2024-35803}\n- ubi: fastmap: Fix duplicate slab cache names while attaching {CVE-2024-53172}\n- ext4: detect invalid INLINE_DATA + EXTENTS flag combination {CVE-2025-40167}\n- nbd: defer config unlock in nbd_genl_connect {CVE-2025-68366}\n- proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al {CVE-2025-38653}\n- block: mark GFP_NOIO around sysfs -\u003estore() {CVE-2025-21817}\n- dlm: fix possible lkb_resource null dereference {CVE-2024-47809}\n- xfs: factor out xfs_attr3_leaf_init\n- crypto: qat - flush misc workqueue during device shutdown {CVE-2025-39721}\n- skbuff: Account for tail adjustment during pull operations {CVE-2022-50365}\n- libceph: fix race between delayed_work() and ceph_monc_stop() {CVE-2024-42232}\n- bpf: Fix reference count leak in bpf_prog_test_run_xdp() {CVE-2026-22994}\n- tpm: Cap the number of PCR banks {CVE-2025-71077}\n- ALSA: ctxfi: Limit PTP to a single page {CVE-2026-31602}\n- wifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure {CVE-2026-23444}\n- fuse: Fix missing FOLL_PIN for direct-io {CVE-2024-53219}\n- tracing: Make sure trace_printk() can output as soon as it can be used {CVE-2023-53007}\n- wifi: rtw88: Use devm_kmemdup() in rtw_set_supported_band() {CVE-2025-71273}\n- can: mcp251x: fix deadlock in error path of mcp251x_open {CVE-2026-23357}\n- ice: Fix memory leak in ice_set_ringparam() {CVE-2026-23389}\n- ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers {CVE-2025-21870}\n- idpf: fix memory leak in idpf_vport_rel() {CVE-2026-23023}\n- Octeontx2-af: Add proper checks for fwdata {CVE-2026-23070}\n- mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() {CVE-2022-48972}\n- HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq {CVE-2026-43051}\n- NFSD: NFSv4 file creation neglects setting ACL {CVE-2025-68803}\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23058}\n- net/sched: cls_api: fix error handling causing NULL dereference {CVE-2025-21857}\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() {CVE-2025-40194}\n- wifi: ath11k: fix RCU stall while reaping monitor destination ring {CVE-2024-58097}\n- Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold {CVE-2026-31408}\n- Bluetooth: bcsp: receive data only if registered {CVE-2025-40308}\n- netfilter: nf_tables: release flowtable after rcu grace period on error {CVE-2026-23392}\n- crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id {CVE-2025-68724}\n- rxrpc: fix reference count leak in rxrpc_server_keyring() {CVE-2026-31634}\n- drm/ttm: Avoid NULL pointer deref for evicted BOs {CVE-2025-71083}\n- HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them {CVE-2026-23382}\n- wifi: radiotap: reject radiotap with unknown bits {CVE-2026-23367}\n- can: j1939: make j1939_session_activate() fail if device is no longer registered {CVE-2025-71182}\n- sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}\n- HID: alps: fix NULL pointer dereference in alps_raw_event() {CVE-2026-31625}\n- RDMA/cm: Fix leaking the multicast GID table reference {CVE-2025-71084}\n- netfilter: nf_conntrack_h323: check for zero length in DecodeQ931() {CVE-2026-23455}\n- rtc: check if __rtc_read_time was successful in rtc_timer_do_work() {CVE-2024-56739}\n- can: j1939: j1939_session_destroy(): fix memory leak of skbs {CVE-2024-56645}\n- Bluetooth: btusb: clamp SCO altsetting table indices {CVE-2026-31497}\n- platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() {CVE-2022-50521}\n- x86/CPU: Fix FPDSS on Zen1 {CVE-2026-31628}\n- io_uring: fix filename leak in __io_openat_prep() {CVE-2025-68814}\n- wifi: mac80211: don't WARN for connections on invalid channels {CVE-2025-71227}\n- cpufreq: Avoid a bad reference count on CPU node {CVE-2024-50012}\n- netfilter: ip6t_eui64: reject invalid MAC header for all packets {CVE-2026-31685}\n- wifi: rt2x00usb: fix devres lifetime {CVE-2026-31672}\n- ext4: xattr: fix null pointer deref in ext4_raw_inode() {CVE-2025-68820}\n- Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv() {CVE-2026-31512}\n- xfrm_user: fix info leak in build_report() {CVE-2026-31671}\n- xfrm: clear trailing padding in build_polexpire() {CVE-2026-31664}\n- ipv6: add NULL checks for idev in SRv6 paths {CVE-2026-23442}\n- octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" {CVE-2025-71137}\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() {CVE-2026-23038}\n- ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free {CVE-2025-38105}\n- ALSA: usb-audio: Kill timer properly at removal {CVE-2025-38105}\n- kernel/fork: only call untrack_pfn_clear() on VMAs duplicated for fork() {CVE-2025-22090}\n- mm: (un)track_pfn_copy() fix + doc improvements {CVE-2025-22090}\n- x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() {CVE-2025-22090}\n- io_uring: fix overflow resched cqe reordering {CVE-2024-50060}\n- io_uring: check if we need to reschedule during overflow flush {CVE-2024-50060}\n- virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN {CVE-2025-38048}\n- nvme-tcp: sanitize request list handling {CVE-2025-38264}\n- KVM: arm64: Reassign nested_mmus array behind mmu_lock {CVE-2026-46316}\n- drm/amd/display: Do not skip unrelated mode changes in DSC validation {CVE-2026-31488}\n- drm/xe: Fix an out-of-bounds shift when invalidating TLB {CVE-2025-37761}\n- fuse: reject oversized dirents in page cache {CVE-2026-31694}\n- bpf, sockmap: Avoid using sk_socket after free when sending {CVE-2025-38154}\n- thermal: core: Fix thermal zone device registration error path {CVE-2026-43332}\n- tcp: Don't call reqsk_fastopen_remove() in tcp_conn_request(). {CVE-2025-40186}\n- smb: client: fix OOB reads parsing symlink error response {CVE-2026-31613}\n- drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() {CVE-2025-71099}\n- scsi: sg: Do not sleep in atomic context {CVE-2025-40259}\n- net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect {CVE-2025-38385}\n- iommufd/selftest: Check for overflow in IOMMU_TEST_OP_ADD_RESERVED {CVE-2025-71122}\n- mm: blk-cgroup: fix use-after-free in cgwb_release_workfn() {CVE-2026-31586}\n- net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback {CVE-2026-23013}","status":"published","published":"2026-10-21T06:13:51Z","modified":"2026-10-26T09:43:57.202616396Z","updated_at":"2026-11-02T15:43:45.794021Z"},{"id":"CLSA-2026-1783791447","title":"kernel: Fix of 307 CVEs","description":"- gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully {CVE-2022-48660}\n- ipv4: check for NULL idev in ip_route_use_hint() {CVE-2024-36008}\n- KEYS: trusted: Do not use WARN when encode fails {CVE-2024-36975}\n- Fix userfaultfd_api to return EINVAL as expected {CVE-2024-41027}\n- xhci: Fix null pointer dereference when host dies {CVE-2023-52898}\n- sctp: sysctl: auth_enable: avoid using current-\u003ensproxy {CVE-2025-21638}\n- blk-mq: fix IO hang from sbitmap wakeup race {CVE-2024-26671}\n- net: openvswitch: fix flow memory leak in ovs_flow_cmd_new {CVE-2023-52977}\n- gpiolib: fix memory leak in gpiochip_setup_dev() {CVE-2022-48975}\n- HID: betop: check shape of output reports {CVE-2023-53015}\n- mm/swapfile: add cond_resched() in get_swap_pages() {CVE-2023-52932}\n- HV: hv_balloon: fix memory leak with using debugfs_lookup() {CVE-2023-52937}\n- drm/i915: Fix a memory leak with reused mmap_offset {CVE-2023-53002}\n- ptdma: pt_core_execute_cmd() should use spinlock {CVE-2023-53013}\n- RDMA/core: Fix ib block iterator counter overflow {CVE-2023-53026}\n- Bluetooth: hci_conn: Fix memory leaks {CVE-2023-53018}\n- scsi: target: pscsi: Fix bio_put() for error case {CVE-2024-26760}\n- sctp: Prevent TOCTOU out-of-bounds write {CVE-2025-40331}\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() {CVE-2026-23038}\n- cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() {CVE-2025-40194}\n- ALSA: hda/cs8409: Fix possible NULL dereference {CVE-2024-50160}\n- nbd: don't allow reconnect after disconnect {CVE-2025-21731}\n- openvswitch: fix lockup on tx to unregistering netdev with carrier {CVE-2025-21681}\n- ext4: detect invalid INLINE_DATA + EXTENTS flag combination {CVE-2025-40167}\n- ext4: xattr: fix null pointer deref in ext4_raw_inode() {CVE-2025-68820}\n- net: fix memory leak in skb_segment_list for GRO packets {CVE-2026-22979}\n- wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode {CVE-2025-40321}\n- ipvs: fix ipv4 null-ptr-deref in route error path {CVE-2025-68813}\n- ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping {CVE-2025-40121}\n- i40e: Fix macvlan leak by synchronizing access to mac_filter_hash {CVE-2024-50041}\n- net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc() {CVE-2024-50000}\n- bpf: Fix reference count leak in bpf_prog_test_run_xdp() {CVE-2026-22994}\n- xsk: check IFF_UP earlier in Tx path {CVE-2023-53240}\n- firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers {CVE-2024-41038}\n- virtgpu: don't reset on shutdown {CVE-2025-38064}\n- xen/netfront: fix crash when removing device {CVE-2022-48969}\n- mptcp: do not fallback when OoO is present {CVE-2024-50185}\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler {CVE-2025-39925}\n- netfilter: nf_tables: remove redundant chain validation on register store {CVE-2025-71160}\n- xfs: fix use-after-free in xattr node block inactivation {CVE-2026-43053}\n- ext4: fix racy may inline data check in dio write {CVE-2023-52786}\n- drm/amdgpu/fence: Fix oops due to non-matching drm_sched init/fini {CVE-2023-52738}\n- macsec: fix UAF bug for real_dev {CVE-2022-49390}\n- drm/i915/gem: Fix Virtual Memory mapping boundaries calculation {CVE-2024-42259}\n- mm/shmem: disable PMD-sized page cache if needed {CVE-2024-42241}\n- driver: iio: add missing checks on iio_info's callback access {CVE-2024-46715}\n- udmabuf: fix memory leak on last export_udmabuf() error path {CVE-2024-56712}\n- ALSA: control: Avoid WARN() for symlink errors {CVE-2024-56657}\n- mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM {CVE-2024-56611}\n- eth: bnxt: always recalculate features after XDP clearing, fix null-deref {CVE-2025-21682}\n- net: annotate data-races around sk-\u003esk_{data_ready,write_space} {CVE-2026-23302}\n- udmabuf: change folios array from kmalloc to kvmalloc {CVE-2024-56544}\n- RDMA/mlx5: Move events notifier registration to be after device registration {CVE-2024-53224}\n- dlm: fix possible lkb_resource null dereference {CVE-2024-47809}\n- ACPI: battery: Fix possible crash when unregistering a battery hook {CVE-2024-49955}\n- ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params {CVE-2024-58012}\n- tpm: Change to kvalloc() in eventlog/acpi.c {CVE-2024-58005}\n- net_sched: sch_sfq: move the limit validation {CVE-2025-37752}\n- usb: xhci: Fix NULL pointer dereference on certain command aborts {CVE-2024-57981}\n- mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize() {CVE-2025-21861}\n- bpf: avoid holding freeze_mutex during mmap operation {CVE-2025-21853}\n- acct: perform last write from workqueue {CVE-2025-21846}\n- netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree() {CVE-2025-21959}\n- ipvlan: ensure network headers are in skb linear part {CVE-2025-21891}\n- wifi: iwlwifi: mvm: fix 6 GHz scan construction {CVE-2024-53055}\n- signal: restore the override_rlimit logic {CVE-2024-50271}\n- thermal: core: Reference count the zone in thermal_zone_get_by_id() {CVE-2024-50028}\n- block: fix potential invalid pointer dereference in blk_add_partition {CVE-2024-47705}\n- userfaultfd: fix checks for huge PMDs {CVE-2024-46787}\n- mptcp: pm: only mark 'subflow' endp as available {CVE-2024-45010}\n- mptcp: pm: re-using ID of unused flushed subflows {CVE-2024-45010}\n- eth: bnxt: fix truesize for mb-xdp-pass case {CVE-2025-21961}\n- driver core: fix potential NULL pointer dereference in dev_uevent() {CVE-2025-37800}\n- virtio_net: Fix napi_skb_cache_put warning {CVE-2024-43835}\n- cgroup: fix race between task migration and iteration {CVE-2026-43439}\n- bpf: Fix wrong reg type conversion in release_reference() {CVE-2022-49873}\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error {CVE-2025-21732}\n- serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN {CVE-2026-23472}\n- drm/amdgpu: Limit BO list entry count to prevent resource exhaustion {CVE-2026-23468}\n- net: add proper RCU protection to /proc/net/ptype {CVE-2026-23255}\n- tcp: secure_seq: add back ports to TS offset {CVE-2026-23247}\n- RDMA/mlx5: Fix a WARN during dereg_mr for DM type {CVE-2025-21888}\n- list: fix a data-race around ep-\u003erdllist {CVE-2022-49443}\n- can: isotp: sanitize CAN ID checks in isotp_bind() {CVE-2022-49269}\n- rxrpc: Fix recv-recv race of completed call {CVE-2025-38524}\n- sched/rt: Fix race in push_rt_task {CVE-2025-38234}\n- NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}\n- virtio: break and reset virtio devices on device_shutdown() {CVE-2025-38064}\n- block: fix resource leak in blk_register_queue() error path {CVE-2025-37980}\n- xsk: Fix race condition in AF_XDP generic RX path {CVE-2025-37920}\n- mm/vmscan: don't try to reclaim hwpoison folio {CVE-2025-37834}\n- nouveau: offload fence uevents work to workqueue {CVE-2024-26719}\n- bpf: Fix kmemleak warning for percpu hashmap {CVE-2025-37807}\n- x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault() {CVE-2024-26906}\n- x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h {CVE-2024-26906}\n- net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket {CVE-2024-42246}\n- quota: Fix potential NULL pointer dereference {CVE-2024-26878}\n- arp: Prevent overflow in arp_req_get(). {CVE-2024-26733}\n- ALSA: Fix deadlocks with kctl removals at disconnection {CVE-2024-38600}\n- wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values {CVE-2024-42114}\n- Bluetooth: hci_core: cancel all works upon hci_unregister_dev() {CVE-2024-41063}\n- fsnotify: clear PARENT_WATCHED flags lazily {CVE-2024-47660}\n- mm: use memalloc_nofs_save() in page_cache_ra_order() {CVE-2024-36882}\n- mm/memory-failure: fix deadlock when hugetlb_optimize_vmemmap is enabled {CVE-2024-26987}\n- net: esp: fix bad handling of pages from page_pool {CVE-2024-26953}\n- virtio/vsock: Fix accept_queue memory leak {CVE-2024-53119}\n- netfilter: nft_payload: sanitize offset and length before calling skb_checksum() {CVE-2024-50251}\n- fs/proc: fix softlockup in __read_vmcore (part 2) {CVE-2025-21694}\n- drm/i915/hdcp: Add encoder check in intel_hdcp_get_capability {CVE-2024-53051}\n- net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod. {CVE-2025-23143}\n- x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() {CVE-2025-22090}\n- net: decrease cached dst counters in dst_release {CVE-2025-22057}\n- nfsd: put dl_stid if fail to queue dl_recall {CVE-2025-22025}\n- nfsd: make nfsd4_run_cb a bool return function {CVE-2025-22025}\n- usb: gadget: core: flush gadget workqueue after device removal {CVE-2025-21838}\n- PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 {CVE-2025-21831}\n- media: uvcvideo: Fix crash during unbind if gpio unit is in use {CVE-2024-58079}\n- usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm() {CVE-2023-52877}\n- ext4: filesystems without casefold feature cannot be mounted with siphash {CVE-2024-49968}\n- padata: use integer wrap around to prevent deadlock on seq_nr overflow {CVE-2024-47739}\n- bpf, lsm: Add check for BPF LSM return value {CVE-2024-47703}\n- sched/smt: Fix unbalance sched_smt_present dec/inc {CVE-2024-44958}\n- xen-netfront: Fix NULL sring after live migration {CVE-2022-48969}\n- dlm: prevent NPD when writing a positive value to event_done {CVE-2025-23131}\n- udp: Deal with race between UDP socket address change and rehash {CVE-2024-57974}\n- bpf: sync_linked_regs() must preserve subreg_def {CVE-2024-53125}\n- mptcp: handle consistently DSS corruption {CVE-2024-50185}\n- null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' {CVE-2024-36478}\n- net: tunnels: annotate lockless accesses to dev-\u003eneeded_headroom {CVE-2023-53109}\n- net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled {CVE-2025-38039}\n- uprobes: Reject the shared zeropage in uprobe_write_opcode() {CVE-2025-21881}\n- mm: slub: avoid wake up kswapd in set_track_prepare {CVE-2025-39843}\n- mm/smaps: fix race between smaps_hugetlb_range and migration {CVE-2025-39754}\n- bpf: Reject narrower access to pointer ctx fields {CVE-2025-38591}\n- net: clear the dst when changing skb protocol {CVE-2025-38192}\n- backlight: led_bl: Hold led_access lock when calling led_sysfs_disable() {CVE-2025-23144}\n- RDMA/core: Don't expose hw_counters outside of init net namespace {CVE-2025-22089}\n- can: j1939: implement NETDEV_UNREGISTER notification handler {CVE-2025-39925}\n- net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF. {CVE-2025-22111}\n- vxlan: Fix NPD when refreshing an FDB entry with a nexthop object {CVE-2025-39851}\n- loop: Avoid updating block size under exclusive owner {CVE-2025-38709}\n- wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() {CVE-2025-38643}\n- net_sched: sch_sfq: reject invalid perturb period {CVE-2025-38193}\n- net: phy: mscc: Fix memory leak when using one step timestamping {CVE-2025-38148}\n- espintcp: remove encap socket caching to avoid reference leak {CVE-2025-38097}\n- rseq: Fix segfault on registration when rseq_cs is non-zero {CVE-2025-38067}\n- serial: mctrl_gpio: split disable_ms into sync and no_sync APIs {CVE-2025-38040}\n- usb: typec: ucsi: displayport: Fix deadlock {CVE-2025-37967}\n- ipvs: fix uninit-value for saddr in do_output_route4 {CVE-2025-37961}\n- ksm: use range-walk function to jump over holes in scan_get_next_rmap_item {CVE-2025-68211}\n- bpf: Scrub packet on bpf_redirect_peer {CVE-2025-37959}\n- tracing: Verify event formats that have \"%*p..\" {CVE-2025-37938}\n- iommu/amd/pgtbl: Fix possible race while increase page table level {CVE-2025-39961}\n- net/mlx5e: Harden uplink netdev access against device unbind {CVE-2025-39947}\n- dm-stripe: fix a possible integer overflow {CVE-2025-39940}\n- net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer {CVE-2025-39937}\n- can: netlink: can_changelink(): fix NULL pointer deref of struct can_priv::do_set_mode {CVE-2025-38665}\n- net/mlx5e: Fix crash on profile change rollback failure {CVE-2026-23000}\n- netfilter: nft_set_pipapo: prevent overflow in lookup table allocation {CVE-2025-38162}\n- tracing: Add recursion protection in kernel stack trace recording {CVE-2026-23138}\n- rxrpc: Fix recvmsg() unconditional requeue {CVE-2026-23066}\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts {CVE-2026-22997}\n- net: can: j1939: recover socket queue on CAN bus error during BAM transmission {CVE-2026-22997}\n- dm-verity: disable recursive forward error correction {CVE-2025-71161}\n- netfilter: nf_tables: avoid chain re-validation if possible {CVE-2025-71160}\n- KEYS: trusted: Fix a memory leak in tpm2_load_cmd {CVE-2025-71147}\n- vsock/virtio: fix potential underflow in virtio_transport_get_credit() {CVE-2026-23069}\n- net: fix segmentation of forwarding fraglist GRO {CVE-2026-23154}\n- ice: Don't process extts if PTP is disabled {CVE-2024-42107}\n- drm/i915/dpt: Make DPT object unshrinkable {CVE-2024-40924}\n- drm/i915/dpt: Treat the DPT BO as a framebuffer {CVE-2024-40924}\n- bpf: Add sk_is_inet and IS_ICSK check in tls_sw_has_ctx_tx/rx {CVE-2024-53091}\n- pipe: wakeup wr_wait after setting max_usage {CVE-2023-52672}\n- bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails {CVE-2023-53103}\n- HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check {CVE-2024-57993}\n- drm/amdkfd: debugfs hang_hws skip GPU with MES {CVE-2025-37853}\n- leds: mlxreg: Use devm_mutex_init() for mutex initialization {CVE-2024-42129}\n- drm/amd/display: fix a Null pointer dereference vulnerability {CVE-2025-39705}\n- gfs2: Validate i_depth for exhash directories {CVE-2025-38710}\n- drm/scheduler: signal scheduled fence when kill job {CVE-2025-38436}\n- drm/amdgpu: Add basic validation for RAS header {CVE-2025-38426}\n- mptcp: fix NULL pointer in can_accept_new_subflow {CVE-2025-23145}\n- bpf: bpf_sk_storage: Fix invalid wait context lockdep report {CVE-2023-53857}\n- nvme-core: fix memory leak in dhchap_secret_store {CVE-2023-53852}\n- virtio_net: Fix error unwinding of XDP initialization {CVE-2023-53499}\n- nvme-core: fix memory leak in dhchap_ctrl_secret {CVE-2023-53792}\n- ceph: fix race condition validating r_parent before applying state {CVE-2025-39927}\n- x86/MCE: Always save CS register on AMD Zen IF Poison errors {CVE-2023-53438}\n- genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask() {CVE-2023-53332}\n- nfsd: move init of percpu reply_cache_stats counters back to nfsd_init_net {CVE-2023-54276}\n- blk-cgroup: Fix NULL deref caused by blkg_policy_data being installed before init {CVE-2023-54271}\n- net/mlx5e: TC, Fix internal port memory leak {CVE-2023-53999}\n- tipc: do not update mtu if msg_max is too small in mtu negotiation {CVE-2023-53517}\n- tipc: add tipc_bearer_min_mtu to calculate min mtu {CVE-2023-53517}\n- tun: Fix memory leak for detached NAPI queue. {CVE-2023-53685}\n- net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize {CVE-2023-53667}\n- start_kernel: Add __no_stack_protector function attribute {CVE-2023-53491}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- sched/psi: use kernfs polling functions for PSI trigger polling {CVE-2023-54019}\n- cxl/pmem: Fix nvdimm registration races {CVE-2023-54323}\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock {CVE-2025-68223}\n- dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() {CVE-2026-23004}\n- wifi: mac80211: don't WARN for connections on invalid channels {CVE-2025-71227}\n- md: suspend array while updating raid_disks via sysfs {CVE-2025-71225}\n- net: stmmac: fix the crash issue for zero copy XDP_TX action {CVE-2025-71095}\n- drm/ttm: Don't leak a resource on eviction error {CVE-2023-54254}\n- firmware: arm_sdei: Fix sleep from invalid context BUG {CVE-2023-54160}\n- iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter {CVE-2023-54057}\n- net: usb: asix: validate PHY address before use {CVE-2025-71094}\n- tty: fix deadlock caused by calling printk() under tty_port-\u003elock {CVE-2022-49441}\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE {CVE-2026-23401}\n- blktrace: fix __this_cpu_read/write in preemptible context {CVE-2026-23374}\n- x86/CPU: Fix FPDSS on Zen1 {CVE-2025-54505}\n- ice: Fix PTP NULL pointer dereference during VSI rebuild {CVE-2026-23210}\n- mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() {CVE-2026-23169}\n- gfs2: No more self recovery {CVE-2025-38659}\n- tracing: kprobe: Fix memory leak in test_gen_kprobe/kretprobe_cmd() {CVE-2022-49891}\n- tracing: kprobe: Fix potential null-ptr-deref on trace_array in kprobe_event_gen_test_exit() {CVE-2022-49796}\n- tracing: kprobe: Fix potential null-ptr-deref on trace_event_file in kprobe_event_gen_test_exit() {CVE-2022-49797}\n- netlink: Bounds-check struct nlmsgerr creation {CVE-2022-49766}\n- bpf: Prevent bpf program recursion for raw tracepoint probes {CVE-2022-49764}\n- i2c: designware: use casting of u64 in clock multiplication to avoid overflow {CVE-2022-49749}\n- futex: Clear stale exiting pointer in futex_lock_pi() retry path {CVE-2026-31555}\n- ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() {CVE-2026-31531}\n- netfilter: ctnetlink: use netlink policy range checks {CVE-2026-31495}\n- tracing: Fix potential deadlock in cpu hotplug with osnoise {CVE-2026-31480}\n- esp: fix skb leak with espintcp and async crypto {CVE-2026-31518}\n- xfs: factor out xfs_attr3_leaf_init {CVE-2026-43053}\n- xfs: factor out xfs_attr3_node_entry_remove {CVE-2026-43053}\n- ALSA: ctxfi: Check the error for index mapping {CVE-2026-31777}\n- bridge: br_nd_send: validate ND option lengths {CVE-2026-31752}\n- rtnetlink: add missing netlink_ns_capable() check for peer netns {CVE-2026-31692}\n- crypto: af_alg - limit RX SG extraction by receive buffer budget {CVE-2026-31677}\n- APEI/GHES: ensure that won't go past CPER allocated record {CVE-2026-43277}\n- ceph: supply snapshot context in ceph_zero_partial_object() {CVE-2026-43273}\n- team: avoid NETDEV_CHANGEMTU event when unregistering slave {CVE-2026-43234}\n- wifi: rtw88: 8822b: Avoid WARNING in rtw8822b_config_trx_mode() {CVE-2025-71297}\n- EFI/CPER: don't go past the ARM processor CPER record buffer {CVE-2026-43266}\n- net: bridge: switchdev: Skip MDB replays of deferred events on offload {CVE-2024-26837}\n- can: mcp251xfd: fix infinite loop when xmit fails {CVE-2024-41088}\n- ipvlan: Make the addrs_lock be per port {CVE-2026-23103}\n- netem: fix return value if duplicate enqueue fails {CVE-2024-45016}\n- USB: serial: mos7840: fix crash on resume {CVE-2024-42244}\n- crypto: null - Use spin lock instead of mutex {CVE-2025-37808}\n- RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly {CVE-2025-71096}\n- bpf: Fix overrunning reservations in ringbuf {CVE-2024-41009}\n- bpf: Fix bpf_sk_select_reuseport() memory leak {CVE-2025-21683}\n- drm/i915: Fix request ref counting during error capture \u0026 debugfs dump {CVE-2023-52981}\n- netfilter: conntrack: fix wrong ct-\u003etimeout value {CVE-2023-53635}\n- drop_monitor: replace spin_lock by raw_spin_lock {CVE-2024-40980}\n- net: bonding: fix NULL deref in bond_debug_rlb_hash_show {CVE-2026-31546}\n- serial: protect uart_port_dtr_rts() in uart_shutdown() too {CVE-2024-50058}\n- wifi: mac80211: Fix static_branch_dec() underflow for aql_disable. {CVE-2026-31551}\n- ipv6: Fix signed integer overflow in __ip6_append_data {CVE-2022-49728}\n- selinux: avoid dereference of garbage after mount failure {CVE-2024-35904}\n- fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name {CVE-2024-49934}\n- tracing: Do not let histogram values have some modifiers {CVE-2023-53093}\n- ice: Add netif_device_attach/detach into PF reset flow {CVE-2024-46770}\n- bpf: Fix deadlock between rcu_tasks_trace and event_mutex. {CVE-2025-37884}\n- fbmon: prevent division by zero in fb_videomode_from_videomode() {CVE-2024-35922}\n- drm/amdgpu: Fix the null pointer dereference to ras_manager {CVE-2024-43908}\n- tracing: Ensure visibility when inserting an element into tracing_map {CVE-2024-26645}\n- drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func {CVE-2024-47720}\n- phy: mdio: fix memory leak {CVE-2021-47416}\n- ipv4: Fix reference count leak when using error routes with nexthop objects {CVE-2025-71097}\n- NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() {CVE-2024-50046}\n- packet: annotate data-races around ignore_outgoing {CVE-2024-26862}\n- md: fix resync softlockup when bitmap size is less than array size {CVE-2024-38598}\n- wireguard: receive: annotate data-race around receiving_counter.counter {CVE-2024-26861}\n- netfs: Only call folio_start_fscache() one time for each folio {CVE-2023-52582}\n- usb: xhci: tegra: fix sleep in atomic call {CVE-2023-53475}\n- ACPI: PAD: fix crash in exit_round_robin() {CVE-2024-49935}\n- locking/rtmutex: Skip remove_waiter() when waiter is not enqueued {CVE-2026-43499}\n- rtmutex: Use waiter::task instead of current in remove_waiter() {CVE-2026-43499}\n- netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6() {CVE-2024-50256}\n- Bluetooth: ISO: Fix multiple init when debugfs is disabled {CVE-2024-50077}\n- hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio {CVE-2025-21931}\n- RDMA/core: Silence oversized kvmalloc() warning {CVE-2025-37867}\n- tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() {CVE-2024-26663}\n- net: let net.core.dev_weight always be non-zero {CVE-2025-21806}\n- net: mdio: fix unbalanced fwnode reference count in mdio_device_release() {CVE-2022-48961}\n- eth: alx: take rtnl_lock on resume {CVE-2022-50498}\n- ata: libata-transport: fix error handling in ata_tlink_add() {CVE-2022-49824}\n- ata: libata-transport: fix error handling in ata_tport_add() {CVE-2022-49825}\n- netfilter: br_netfilter: fix panic with metadata_dst skb {CVE-2024-50045}\n- net: fix NULL pointer in skb_segment_list {CVE-2023-52991}\n- hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove {CVE-2024-26698}\n- scsi: qla2xxx: validate nvme_local_port correctly {CVE-2024-42286}\n- rcu/rcuscale: Stop kfree_scale_thread thread(s) after unloading rcuscale {CVE-2023-53291}\n- wifi: mac80211: Discard Beacon frames to non-broadcast address {CVE-2025-71127}\n- wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() {CVE-2024-46755}\n- sctp: sysctl: cookie_hmac_alg: avoid using current-\u003ensproxy {CVE-2025-21640}\n- drm/nouveau/dispnv04: fix null pointer dereference in nv17_tv_get_hd_modes {CVE-2024-41089}\n- tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING {CVE-2023-52845}\n- bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets {CVE-2023-52523}\n- Bluetooth: Fix not cleanup led when bt_init fails {CVE-2022-48971}\n- netfilter: nf_conntrack_h323: Add protection for bmp length out of range {CVE-2024-26851}\n- ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() {CVE-2024-53680}\n- ppp_async: limit MRU to 64K {CVE-2024-26675}\n- USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages {CVE-2024-40904}\n- ipv6: mcast: fix data-race in ipv6_mc_down / mld_ifc_work {CVE-2024-26631}\n- xfrm: fix one more kernel-infoleak in algo dumping {CVE-2024-50110}\n- xdp: fix invalid wait context of page_pool_destroy() {CVE-2024-43834}\n- fs/netfs/fscache_cookie: add missing \"n_accesses\" check {CVE-2024-45000}\n- mac802154: check local interfaces before deleting sdata list {CVE-2024-57948}\n- usbnet: gl620a: fix endpoint checking in genelink_bind() {CVE-2025-21877}\n- IB/core: Fix ib_cache_setup_one error flow cleanup {CVE-2024-47693}\n- can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate {CVE-2021-4454}\n- vfs: fix race between evice_inodes() and find_inode()\u0026iput() {CVE-2024-47679}\n- scsi: storvsc: Fix handling of virtual Fibre Channel timeouts {CVE-2023-53245}\n- iavf: fix off-by-one issues in iavf_config_rss_reg() {CVE-2025-71087}\n- cachefiles: fix memory leak in cachefiles_add_cache() {CVE-2024-26840}\n- ext4: fix access to uninitialised lock in fc replay path {CVE-2024-50014}\n- net: hns3: fix kernel crash when 1588 is sent on HIP08 devices {CVE-2025-21649}\n- ftrace: Fix regression with module command in stack_trace_filter {CVE-2024-56569}\n- ipv6: sr: fix invalid unregister error path {CVE-2024-38612}\n- crypto: pcrypt - Fix handling of MAY_BACKLOG requests {CVE-2026-43493}\n- netfilter: flowtable: strictly check for maximum number of actions {CVE-2026-43329}\n- ipv6: icmp: clear skb2-\u003ecb[] in ip6_err_gen_icmpv6_unreach() {CVE-2026-43038}","status":"published","published":"2026-10-21T12:13:51Z","modified":"2026-10-26T09:43:27.885610959Z","updated_at":"2026-11-02T15:43:46.151924Z"},{"id":"CVE-2026-23138","title":"tracing: Add recursion protection in kernel stack trace recording","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.","status":"published","published":"2026-02-14T15:22:23.385Z","modified":"2026-11-07T02:30:46.62199605Z","updated_at":"2026-11-07T03:06:12.570613Z"},{"id":"openSUSE-SU-2026:20572-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T17:16:35Z","modified":"2026-04-22T08:16:13.517421Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"SUSE-SU-2026:21230-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:11:07Z","modified":"2026-07-09T18:29:49.212435035Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21237-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:44:52Z","modified":"2026-04-23T18:26:50.344244Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21352-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:09:00Z","modified":"2026-04-29T18:23:57.904042Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"SUSE-SU-2026:21361-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow (bsc#1252073).\n- CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).\n- CVE-2025-68794: iomap: adjust read range correctly for non-block-aligned positions (bsc#1256647).\n- CVE-2025-71239: audit: add fchmodat2() to change attributes class (bsc#1259759).\n- CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv() (bsc#1257708).\n- CVE-2026-23103: ipvlan: Make the addrs_lock be per port (bsc#1257773).\n- CVE-2026-23120: l2tp: avoid one data-race in l2tp_tunnel_del_work() (bsc#1258280).\n- CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).\n- CVE-2026-23138: kABI: Preserve values of the trace recursion bits (bsc#1258301).\n- CVE-2026-23140: bpf, test_run: Subtract size of xdp_frame from allowed metadata size (bsc#1258305).\n- CVE-2026-23187: pmdomain: imx8m-blk-ctrl: fix out-of-range access of bc-\u003edomains (bsc#1258330).\n- CVE-2026-23193: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (bsc#1258414).\n- CVE-2026-23201: ceph: fix oops due to invalid pointer for kfree() in parse_longname() (bsc#1258337).\n- CVE-2026-23204: net: add skb_header_pointer_careful() helper (bsc#1258340).\n- CVE-2026-23215: x86/vmware: Fix hypercall clobbers (bsc#1258476).\n- CVE-2026-23216: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (bsc#1258447).\n- CVE-2026-23231: netfilter: nf_tables: fix use-after-free in nf_tables_addchain() (bsc#1259188).\n- CVE-2026-23239: espintcp: Fix race condition in espintcp_close() (bsc#1259485).\n- CVE-2026-23240: tls: Fix race condition in tls_sw_cancel_work_tx() (bsc#1259484).\n- CVE-2026-23242: RDMA/siw: Fix potential NULL pointer dereference in header processing (bsc#1259795).\n- CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write (bsc#1259797).\n- CVE-2026-23255: net: add proper RCU protection to /proc/net/ptype (bsc#1259891).\n- CVE-2026-23262: gve: Fix stats report corruption on queue count change (bsc#1259870).\n- CVE-2026-23270: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks (bsc#1259886).\n- CVE-2026-23272: netfilter: nf_tables: unconditionally bump set-\u003enelems before insertion (bsc#1260009).\n- CVE-2026-23274: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels (bsc#1260005).\n- CVE-2026-23277: net/sched: teql: fix NULL pointer dereference in iptunnel_xmit on TEQL slave xmit (bsc#1259997).\n- CVE-2026-23278: netfilter: nf_tables: always walk all pending catchall elements (bsc#1259998).\n- CVE-2026-23281: wifi: libertas: fix use-after-free in lbs_free_adapter() (bsc#1260464).\n- CVE-2026-23292: scsi: target: Fix recursive locking in __configfs_open_file() (bsc#1260500).\n- CVE-2026-23293: net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260486).\n- CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit() (bsc#1260490).\n- CVE-2026-23304: ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() (bsc#1260544).\n- CVE-2026-23319: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim (bsc#1260735).\n- CVE-2026-23326: xsk: Fix fragment node deletion to prevent buffer leak (bsc#1260606).\n- CVE-2026-23335: RDMA/irdma: Fix kernel stack leak in irdma_create_user_ah() (bsc#1260550).\n- CVE-2026-23343: xdp: produce a warning when calculated tailroom is negative (bsc#1260527).\n- CVE-2026-23361: PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry (bsc#1260732).\n- CVE-2026-23379: net/sched: ets: fix divide by zero in the offload path (bsc#1260481).\n- CVE-2026-23381: net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled (bsc#1260471).\n- CVE-2026-23383: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing (bsc#1260497).\n- CVE-2026-23386: gve: fix incorrect buffer cleanup in gve_tx_clean_pending_packets for QPL (bsc#1260799).\n- CVE-2026-23393: bridge: cfm: Fix race condition in peer_mep deletion (bsc#1260522).\n- CVE-2026-23398: icmp: fix NULL pointer dereference in icmp_tag_validation() (bsc#1260730).\n- CVE-2026-23413: clsact: Fix use-after-free in init/destroy rollback asymmetry (bsc#1261498).\n- CVE-2026-23414: tls: Purge async_hold in tls_decrypt_async_wait() (bsc#1261496).\n- CVE-2026-23419: net/rds: Fix circular locking dependency in rds_tcp_tune (bsc#1261507).\n- CVE-2026-23425: KVM: arm64: Fix ID register initialization for non-protected pKVM guests (bsc#1261506).\n- CVE-2026-31788: xen/privcmd: restrict usage in unprivileged domU (bsc#1259707).\n\nThe following non security issues were fixed:\n\n- KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE (bsc#1259461).\n- KVM: x86: synthesize CPUID bits only if CPU capability is set (bsc#1257511).\n- Revert \"drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\"\n- Update config files (bsc#1254307).\n- apparmor: Fix double free of ns_name in aa_replace_profiles() (bsc#1258849).\n- apparmor: fix differential encoding verification (bsc#1258849).\n- apparmor: fix memory leak in verify_header (bsc#1258849).\n- apparmor: fix missing bounds check on DEFAULT table in verify_dfa() (bsc#1258849).\n- apparmor: fix race between freeing data and fs accessing it (bsc#1258849).\n- apparmor: fix race on rawdata dereference (bsc#1258849).\n- apparmor: fix side-effect bug in match_char() macro usage (bsc#1258849).\n- apparmor: fix unprivileged local user can do privileged policy management (bsc#1258849).\n- apparmor: fix: limit the number of levels of policy namespaces (bsc#1258849).\n- apparmor: replace recursive profile removal with iterative approach (bsc#1258849).\n- apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1258849).\n- bpf, btf: Enforce destructor kfunc type with CFI (bsc#1259955).\n- bpf: crypto: Use the correct destructor kfunc type (bsc#1259955).\n- btrfs: only enforce free space tree if v1 cache is required for bs \u003c ps cases (bsc#1260459).\n- btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() (bsc#1257777).\n- dmaengine: sh: rz-dmac: Move CHCTRL updates under spinlock (git-fixes).\n- drm/amdkfd: Unreserve bo if queue update failed (git-fixes).\n- drm/i915/display: Add module param to skip retraining of dp link (bsc#1253129).\n- drm/i915/dsc: Add Selective Update register definitions (stable-fixes).\n- drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters (stable-fixes).\n- firmware: microchip: fail auto-update probe if no flash found (git-fixes).\n- kABI: Include trace recursion bits in kABI tracking (bsc#1258301).\n- net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout (bsc#1259580).\n- nvme: add support for dynamic quirk configuration via module parameter (bsc#1243208).\n- nvme: expose active quirks in sysfs (bsc#1243208).\n- nvme: fix memory leak in quirks_param_set() (bsc#1243208).\n- powerpc/crash: adjust the elfcorehdr size (jsc#PED-11175 git-fixes).\n- powerpc/kdump: Fix size calculation for hot-removed memory ranges (jsc#PED-11175 git-fixes).\n- s390/cio: Update purge function to unregister the unused subchannels (bsc#1254214).\n- s390/ipl: Clear SBP flag when bootprog is set (bsc#1258175).\n- s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP (bsc#1254306).\n- scsi: fnic: Add Cisco hardware model names (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FDMI (jsc#PED-15441).\n- scsi: fnic: Add and integrate support for FIP (jsc#PED-15441).\n- scsi: fnic: Add functionality in fnic to support FDLS (jsc#PED-15441).\n- scsi: fnic: Add headers and definitions for FDLS (jsc#PED-15441).\n- scsi: fnic: Add stats and related functionality (jsc#PED-15441).\n- scsi: fnic: Add support for fabric based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for target based solicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support for unsolicited requests and responses (jsc#PED-15441).\n- scsi: fnic: Add support to handle port channel RSCN (jsc#PED-15441).\n- scsi: fnic: Code cleanup (jsc#PED-15441).\n- scsi: fnic: Delete incorrect debugfs error handling (jsc#PED-15441).\n- scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out (jsc#PED-15441).\n- scsi: fnic: Fix indentation and remove unnecessary parenthesis (jsc#PED-15441).\n- scsi: fnic: Fix missing DMA mapping error in fnic_send_frame() (jsc#PED-15441).\n- scsi: fnic: Fix use of uninitialized value in debug message (jsc#PED-15441).\n- scsi: fnic: Increment driver version (jsc#PED-15441).\n- scsi: fnic: Modify IO path to use FDLS (jsc#PED-15441).\n- scsi: fnic: Modify fnic interfaces to use FDLS (jsc#PED-15441).\n- scsi: fnic: Propagate SCSI error code from fnic_scsi_drv_init() (jsc#PED-15441).\n- scsi: fnic: Remove always-true IS_FNIC_FCP_INITIATOR macro (jsc#PED-15441).\n- scsi: fnic: Remove extern definition from .c files (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary debug print (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else and unnecessary break in FDLS (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary else to fix warning in FDLS FIP (jsc#PED-15441).\n- scsi: fnic: Remove unnecessary spinlock locking and unlocking (jsc#PED-15441).\n- scsi: fnic: Replace fnic-\u003elock_flags with local flags (jsc#PED-15441).\n- scsi: fnic: Replace shost_printk() with dev_info()/dev_err() (jsc#PED-15441).\n- scsi: fnic: Replace use of sizeof with standard usage (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code for mem alloc failure (jsc#PED-15441).\n- scsi: fnic: Return appropriate error code from failure of scsi drv init (jsc#PED-15441).\n- scsi: fnic: Test for memory allocation failure and return error code (jsc#PED-15441).\n- scsi: fnic: Turn off FDMI ACTIVE flags on link down (jsc#PED-15441).\n- scsi: hisi_sas: Fix NULL pointer exception during user_scan() (bsc#1255687).\n- scsi: scsi_transport_sas: Fix the maximum channel scanning issue (bsc#1255687, git-fixes).\n- scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() (git-fixes, jsc#PED-15042).\n- selftests/bpf: Use the correct destructor kfunc type (bsc#1259955).\n- selftests/powerpc: Suppress -Wmaybe-uninitialized with GCC 15 (bsc#1261669 ltc#212590).\n- tg3: Fix race for querying speed/duplex (bsc#1257183).\n- x86/platform/uv: Handle deconfigured sockets (bsc#1260347).\n","status":"published","published":"2026-04-20T15:44:52Z","modified":"2026-04-29T18:23:57.770283Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"USN-8567-1","title":"linux, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320)\n","status":"published","published":"2026-07-20T15:36:35Z","modified":"2026-11-07T01:46:48.030854859Z","updated_at":"2026-11-07T01:56:38.538236Z"},{"id":"USN-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-8574-1","title":"linux-gcp-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-21T09:51:58Z","modified":"2026-11-09T12:46:41.603455464Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8574-2","title":"linux-fips, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T07:48:36Z","modified":"2026-11-09T12:48:51.609882158Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8574-3","title":"linux-ibm, linux-ibm-6.8, linux-nvidia-tegra, linux-xilinx vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43362, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43371, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43386, CVE-2026-43387, CVE-2026-43395,\nCVE-2026-43397, CVE-2026-43405, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43495,\nCVE-2026-43496, CVE-2026-43497, CVE-2026-43499, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45855, CVE-2026-45858, CVE-2026-45899, CVE-2026-45911,\nCVE-2026-45920, CVE-2026-45924, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45956, CVE-2026-45958, CVE-2026-45985, CVE-2026-45986,\nCVE-2026-45987, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46120,\nCVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124,\nCVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128,\nCVE-2026-46129, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46273, CVE-2026-46274, CVE-2026-46280,\nCVE-2026-46282, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-28T07:23:25Z","modified":"2026-11-09T12:49:17.012782847Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-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-8595-1","title":"linux-oracle-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-23T07:57:09Z","modified":"2026-11-09T12:46:39.626735177Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-2","title":"linux-aws vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-24T10:14:09Z","modified":"2026-11-09T12:46:40.833371554Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8595-3","title":"linux-aws-6.8, linux-aws-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64164)\n","status":"published","published":"2026-07-28T07:25:50Z","modified":"2026-11-09T12:49:11.651297869Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8596-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23226, CVE-2026-23227, CVE-2026-23244, CVE-2026-23245,\nCVE-2026-23246, CVE-2026-23253, CVE-2026-23255, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23276, CVE-2026-23277, CVE-2026-23279,\nCVE-2026-23281, CVE-2026-23284, CVE-2026-23285, CVE-2026-23286,\nCVE-2026-23287, CVE-2026-23289, CVE-2026-23290, CVE-2026-23291,\nCVE-2026-23292, CVE-2026-23293, CVE-2026-23296, CVE-2026-23298,\nCVE-2026-23300, CVE-2026-23302, CVE-2026-23303, CVE-2026-23304,\nCVE-2026-23306, CVE-2026-23307, CVE-2026-23308, CVE-2026-23310,\nCVE-2026-23312, CVE-2026-23313, CVE-2026-23315, CVE-2026-23317,\nCVE-2026-23318, CVE-2026-23319, CVE-2026-23321, CVE-2026-23324,\nCVE-2026-23325, CVE-2026-23330, CVE-2026-23334, CVE-2026-23335,\nCVE-2026-23336, CVE-2026-23339, CVE-2026-23340, CVE-2026-23343,\nCVE-2026-23347, CVE-2026-23352, CVE-2026-23356, CVE-2026-23357,\nCVE-2026-23359, CVE-2026-23360, CVE-2026-23361, CVE-2026-23362,\nCVE-2026-23363, CVE-2026-23364, CVE-2026-23365, CVE-2026-23367,\nCVE-2026-23368, CVE-2026-23369, CVE-2026-23370, CVE-2026-23372,\nCVE-2026-23374, CVE-2026-23375, CVE-2026-23378, CVE-2026-23379,\nCVE-2026-23381, CVE-2026-23382, CVE-2026-23383, CVE-2026-23386,\nCVE-2026-23387, CVE-2026-23388, CVE-2026-23389, CVE-2026-23391,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439,\nCVE-2026-23440, CVE-2026-23441, CVE-2026-23442, CVE-2026-23444,\nCVE-2026-23446, CVE-2026-23447, CVE-2026-23448, CVE-2026-23449,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23456, CVE-2026-23457,\nCVE-2026-23458, CVE-2026-23460, CVE-2026-23461, CVE-2026-23462,\nCVE-2026-23463, CVE-2026-23464, CVE-2026-23465, CVE-2026-23468,\nCVE-2026-23470, CVE-2026-23474, CVE-2026-23475, CVE-2026-31389,\nCVE-2026-31391, CVE-2026-31392, CVE-2026-31393, CVE-2026-31394,\nCVE-2026-31396, CVE-2026-31399, CVE-2026-31400, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31412, CVE-2026-31413, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31421, CVE-2026-31422,\nCVE-2026-31423, CVE-2026-31424, CVE-2026-31425, CVE-2026-31426,\nCVE-2026-31427, CVE-2026-31428, CVE-2026-31429, CVE-2026-31430,\nCVE-2026-31432, CVE-2026-31433, CVE-2026-31434, CVE-2026-31438,\nCVE-2026-31439, CVE-2026-31440, CVE-2026-31441, CVE-2026-31446,\nCVE-2026-31447, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53354,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64164)\n","status":"published","published":"2026-07-23T08:06:00Z","modified":"2026-11-09T12:48:44.712103783Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-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"},{"id":"USN-8606-1","title":"linux-azure, linux-azure-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43363, CVE-2026-43365, CVE-2026-43366,\nCVE-2026-43368, CVE-2026-43370, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43378, CVE-2026-43380, CVE-2026-43381,\nCVE-2026-43382, CVE-2026-43383, CVE-2026-43384, CVE-2026-43386,\nCVE-2026-43387, CVE-2026-43395, CVE-2026-43397, CVE-2026-43405,\nCVE-2026-43406, CVE-2026-43407, CVE-2026-43408, CVE-2026-43409,\nCVE-2026-43411, CVE-2026-43412, CVE-2026-43413, CVE-2026-43414,\nCVE-2026-43415, CVE-2026-43419, CVE-2026-43420, CVE-2026-43421,\nCVE-2026-43424, CVE-2026-43425, CVE-2026-43426, CVE-2026-43427,\nCVE-2026-43428, CVE-2026-43429, CVE-2026-43430, CVE-2026-43432,\nCVE-2026-43436, CVE-2026-43437, CVE-2026-43439, CVE-2026-43441,\nCVE-2026-43445, CVE-2026-43448, CVE-2026-43449, CVE-2026-43450,\nCVE-2026-43451, CVE-2026-43452, CVE-2026-43453, CVE-2026-43455,\nCVE-2026-43456, CVE-2026-43457, CVE-2026-43458, CVE-2026-43459,\nCVE-2026-43466, CVE-2026-43467, CVE-2026-43468, CVE-2026-43469,\nCVE-2026-43471, CVE-2026-43472, CVE-2026-43473, CVE-2026-43475,\nCVE-2026-43476, CVE-2026-43480, CVE-2026-43483, CVE-2026-43484,\nCVE-2026-43488, CVE-2026-43490, CVE-2026-43491, CVE-2026-43492,\nCVE-2026-43493, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497,\nCVE-2026-43499, CVE-2026-43501, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45855, CVE-2026-45856, CVE-2026-45857, CVE-2026-45858,\nCVE-2026-45859, CVE-2026-45860, CVE-2026-45861, CVE-2026-45862,\nCVE-2026-45864, CVE-2026-45865, CVE-2026-45866, CVE-2026-45867,\nCVE-2026-45868, CVE-2026-45869, CVE-2026-45870, CVE-2026-45871,\nCVE-2026-45872, CVE-2026-45873, CVE-2026-45875, CVE-2026-45877,\nCVE-2026-45878, CVE-2026-45879, CVE-2026-45880, CVE-2026-45881,\nCVE-2026-45882, CVE-2026-45883, CVE-2026-45884, CVE-2026-45885,\nCVE-2026-45886, CVE-2026-45890, CVE-2026-45891, CVE-2026-45893,\nCVE-2026-45895, CVE-2026-45899, CVE-2026-45902, CVE-2026-45904,\nCVE-2026-45905, CVE-2026-45910, CVE-2026-45911, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45920, CVE-2026-45921,\nCVE-2026-45923, CVE-2026-45924, CVE-2026-45928, CVE-2026-45935,\nCVE-2026-45936, CVE-2026-45938, CVE-2026-45941, CVE-2026-45942,\nCVE-2026-45943, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45956, CVE-2026-45957, CVE-2026-45958,\nCVE-2026-45960, CVE-2026-45962, CVE-2026-45964, CVE-2026-45965,\nCVE-2026-45968, CVE-2026-45969, CVE-2026-45970, CVE-2026-45972,\nCVE-2026-45973, CVE-2026-45974, CVE-2026-45976, CVE-2026-45978,\nCVE-2026-45981, CVE-2026-45982, CVE-2026-45983, CVE-2026-45984,\nCVE-2026-45985, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46043,\nCVE-2026-46044, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049,\nCVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053,\nCVE-2026-46056, CVE-2026-46058, CVE-2026-46061, CVE-2026-46062,\nCVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46068,\nCVE-2026-46069, CVE-2026-46070, CVE-2026-46072, CVE-2026-46073,\nCVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078,\nCVE-2026-46079, CVE-2026-46080, CVE-2026-46082, CVE-2026-46083,\nCVE-2026-46084, CVE-2026-46086, CVE-2026-46088, CVE-2026-46089,\nCVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46094,\nCVE-2026-46098, CVE-2026-46099, CVE-2026-46101, CVE-2026-46102,\nCVE-2026-46103, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108,\nCVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113,\nCVE-2026-46114, CVE-2026-46115, CVE-2026-46116, CVE-2026-46117,\nCVE-2026-46119, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122,\nCVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126,\nCVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46131,\nCVE-2026-46132, CVE-2026-46133, CVE-2026-46135, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46185, CVE-2026-46186,\nCVE-2026-46187, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191,\nCVE-2026-46193, CVE-2026-46194, CVE-2026-46195, CVE-2026-46196,\nCVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200,\nCVE-2026-46201, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206,\nCVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46211,\nCVE-2026-46212, CVE-2026-46214, CVE-2026-46218, CVE-2026-46219,\nCVE-2026-46220, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227,\nCVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232,\nCVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236,\nCVE-2026-46238, CVE-2026-46241, CVE-2026-46243, CVE-2026-46244,\nCVE-2026-46246, CVE-2026-46247, CVE-2026-46249, CVE-2026-46250,\nCVE-2026-46251, CVE-2026-46253, CVE-2026-46254, CVE-2026-46255,\nCVE-2026-46259, CVE-2026-46260, CVE-2026-46261, CVE-2026-46265,\nCVE-2026-46266, CVE-2026-46267, CVE-2026-46270, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46289, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-46328, CVE-2026-52911, CVE-2026-52920,\nCVE-2026-52925, CVE-2026-52933, CVE-2026-52936, CVE-2026-52951,\nCVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958,\nCVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964,\nCVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970,\nCVE-2026-52974, CVE-2026-52975, CVE-2026-52977, CVE-2026-52981,\nCVE-2026-52982, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986,\nCVE-2026-52989, CVE-2026-52990, CVE-2026-52992, CVE-2026-52993,\nCVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001,\nCVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006,\nCVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014,\nCVE-2026-53015, CVE-2026-53016, CVE-2026-53021, CVE-2026-53022,\nCVE-2026-53023, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034,\nCVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53039,\nCVE-2026-53040, CVE-2026-53041, CVE-2026-53043, CVE-2026-53045,\nCVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049,\nCVE-2026-53050, CVE-2026-53052, CVE-2026-53056, CVE-2026-53058,\nCVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062,\nCVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066,\nCVE-2026-53068, CVE-2026-53069, CVE-2026-53071, CVE-2026-53072,\nCVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076,\nCVE-2026-53077, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084,\nCVE-2026-53085, CVE-2026-53086, CVE-2026-53088, CVE-2026-53093,\nCVE-2026-53094, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098,\nCVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53115,\nCVE-2026-53117, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126,\nCVE-2026-53128, CVE-2026-53130, CVE-2026-53279, CVE-2026-53287,\nCVE-2026-53289, CVE-2026-53291, CVE-2026-53293, CVE-2026-53294,\nCVE-2026-53295, CVE-2026-53296, CVE-2026-53303, CVE-2026-53304,\nCVE-2026-53306, CVE-2026-53309, CVE-2026-53314, CVE-2026-53320,\nCVE-2026-53369, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376,\nCVE-2026-53379, CVE-2026-63838, CVE-2026-63843, CVE-2026-63844,\nCVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848,\nCVE-2026-63851, CVE-2026-63852, CVE-2026-63854, CVE-2026-63855,\nCVE-2026-63856, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862,\nCVE-2026-63865, CVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:17:16Z","modified":"2026-11-07T01:46:10.910402805Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8607-1","title":"linux-azure-fde vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:20:29Z","modified":"2026-11-07T01:46:01.058375657Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8608-1","title":"linux-azure-fips vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31638, CVE-2026-31639,\nCVE-2026-31642, CVE-2026-31645, CVE-2026-31646, CVE-2026-31648,\nCVE-2026-31651, CVE-2026-31655, CVE-2026-31656, CVE-2026-31658,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31670, CVE-2026-31671,\nCVE-2026-31672, CVE-2026-31673, CVE-2026-31674, CVE-2026-31675,\nCVE-2026-31677, CVE-2026-31678, CVE-2026-31679, CVE-2026-31680,\nCVE-2026-31681, CVE-2026-31683, CVE-2026-31684, CVE-2026-31686,\nCVE-2026-31689, CVE-2026-31694, CVE-2026-31695, CVE-2026-31696,\nCVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700,\nCVE-2026-31701, CVE-2026-31702, CVE-2026-31704, CVE-2026-31705,\nCVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709,\nCVE-2026-31711, CVE-2026-31712, CVE-2026-31714, CVE-2026-31715,\nCVE-2026-31716, CVE-2026-31720, CVE-2026-31721, CVE-2026-31722,\nCVE-2026-31723, CVE-2026-31724, CVE-2026-31725, CVE-2026-31726,\nCVE-2026-31728, CVE-2026-31729, CVE-2026-31730, CVE-2026-31731,\nCVE-2026-31737, CVE-2026-31738, CVE-2026-31740, CVE-2026-31741,\nCVE-2026-31747, CVE-2026-31748, CVE-2026-31749, CVE-2026-31751,\nCVE-2026-31752, CVE-2026-31754, CVE-2026-31755, CVE-2026-31756,\nCVE-2026-31758, CVE-2026-31759, CVE-2026-31761, CVE-2026-31762,\nCVE-2026-31763, CVE-2026-31767, CVE-2026-31768, CVE-2026-31770,\nCVE-2026-31772, CVE-2026-31773, CVE-2026-31778, CVE-2026-31779,\nCVE-2026-31780, CVE-2026-31781, CVE-2026-31788, CVE-2026-43007,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43040,\nCVE-2026-43041, CVE-2026-43043, CVE-2026-43044, CVE-2026-43046,\nCVE-2026-43047, CVE-2026-43049, CVE-2026-43050, CVE-2026-43051,\nCVE-2026-43052, CVE-2026-43054, CVE-2026-43056, CVE-2026-43057,\nCVE-2026-43058, CVE-2026-43059, CVE-2026-43060, CVE-2026-43061,\nCVE-2026-43062, CVE-2026-43064, CVE-2026-43065, CVE-2026-43066,\nCVE-2026-43068, CVE-2026-43069, CVE-2026-43072, CVE-2026-43073,\nCVE-2026-43074, CVE-2026-43075, CVE-2026-43076, CVE-2026-43079,\nCVE-2026-43080, CVE-2026-43081, CVE-2026-43082, CVE-2026-43084,\nCVE-2026-43085, CVE-2026-43086, CVE-2026-43088, CVE-2026-43089,\nCVE-2026-43091, CVE-2026-43092, CVE-2026-43093, CVE-2026-43094,\nCVE-2026-43098, CVE-2026-43099, CVE-2026-43103, CVE-2026-43104,\nCVE-2026-43105, CVE-2026-43107, CVE-2026-43109, CVE-2026-43110,\nCVE-2026-43111, CVE-2026-43112, CVE-2026-43113, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43129, CVE-2026-43162, CVE-2026-43245,\nCVE-2026-43252, CVE-2026-43265, CVE-2026-43281, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198,\nCVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46204,\nCVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208,\nCVE-2026-46209, CVE-2026-46211, CVE-2026-46212, CVE-2026-46214,\nCVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46225,\nCVE-2026-46226, CVE-2026-46227, CVE-2026-46229, CVE-2026-46230,\nCVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234,\nCVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46241,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46291,\nCVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46296,\nCVE-2026-46299, CVE-2026-46301, CVE-2026-46303, CVE-2026-46304,\nCVE-2026-46306, CVE-2026-46307, CVE-2026-46312, CVE-2026-46314,\nCVE-2026-46319, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:23:19Z","modified":"2026-11-09T12:47:05.283755841Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8609-1","title":"linux-azure-fde-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23220, CVE-2026-23221,\nCVE-2026-23222, CVE-2026-23226, CVE-2026-23227, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23249, CVE-2026-23253,\nCVE-2026-23255, CVE-2026-23266, CVE-2026-23267, CVE-2026-23270,\nCVE-2026-23271, CVE-2026-23272, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23278, CVE-2026-23279, CVE-2026-23281, CVE-2026-23284,\nCVE-2026-23285, CVE-2026-23286, CVE-2026-23287, CVE-2026-23289,\nCVE-2026-23290, CVE-2026-23291, CVE-2026-23292, CVE-2026-23293,\nCVE-2026-23296, CVE-2026-23298, CVE-2026-23300, CVE-2026-23302,\nCVE-2026-23303, CVE-2026-23304, CVE-2026-23306, CVE-2026-23307,\nCVE-2026-23308, CVE-2026-23310, CVE-2026-23312, CVE-2026-23313,\nCVE-2026-23315, CVE-2026-23317, CVE-2026-23318, CVE-2026-23319,\nCVE-2026-23321, CVE-2026-23324, CVE-2026-23325, CVE-2026-23330,\nCVE-2026-23334, CVE-2026-23335, CVE-2026-23336, CVE-2026-23339,\nCVE-2026-23340, CVE-2026-23343, CVE-2026-23347, CVE-2026-23352,\nCVE-2026-23356, CVE-2026-23357, CVE-2026-23359, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23392, CVE-2026-23395, CVE-2026-23396,\nCVE-2026-23397, CVE-2026-23398, CVE-2026-23399, CVE-2026-23401,\nCVE-2026-23412, CVE-2026-23413, CVE-2026-23414, CVE-2026-23418,\nCVE-2026-23419, CVE-2026-23420, CVE-2026-23426, CVE-2026-23428,\nCVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23440,\nCVE-2026-23441, CVE-2026-23442, CVE-2026-23444, CVE-2026-23446,\nCVE-2026-23447, CVE-2026-23448, CVE-2026-23449, CVE-2026-23450,\nCVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31402, CVE-2026-31403, CVE-2026-31405, CVE-2026-31407,\nCVE-2026-31408, CVE-2026-31409, CVE-2026-31411, CVE-2026-31412,\nCVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417,\nCVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423,\nCVE-2026-31424, CVE-2026-31425, CVE-2026-31426, CVE-2026-31427,\nCVE-2026-31428, CVE-2026-31429, CVE-2026-31430, CVE-2026-31432,\nCVE-2026-31433, CVE-2026-31436, CVE-2026-31438, CVE-2026-31439,\nCVE-2026-31440, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447,\nCVE-2026-31448, CVE-2026-31449, CVE-2026-31450, CVE-2026-31451,\nCVE-2026-31452, CVE-2026-31453, CVE-2026-31454, CVE-2026-31455,\nCVE-2026-31458, CVE-2026-31464, CVE-2026-31466, CVE-2026-31467,\nCVE-2026-31469, CVE-2026-31470, CVE-2026-31473, CVE-2026-31474,\nCVE-2026-31476, CVE-2026-31477, CVE-2026-31478, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31506, CVE-2026-31507, CVE-2026-31508,\nCVE-2026-31509, CVE-2026-31510, CVE-2026-31511, CVE-2026-31512,\nCVE-2026-31515, CVE-2026-31516, CVE-2026-31518, CVE-2026-31519,\nCVE-2026-31520, CVE-2026-31521, CVE-2026-31522, CVE-2026-31523,\nCVE-2026-31524, CVE-2026-31525, CVE-2026-31527, CVE-2026-31528,\nCVE-2026-31530, CVE-2026-31532, CVE-2026-31540, CVE-2026-31542,\nCVE-2026-31545, CVE-2026-31546, CVE-2026-31548, CVE-2026-31549,\nCVE-2026-31550, CVE-2026-31551, CVE-2026-31552, CVE-2026-31554,\nCVE-2026-31555, CVE-2026-31556, CVE-2026-31557, CVE-2026-31563,\nCVE-2026-31565, CVE-2026-31566, CVE-2026-31570, CVE-2026-31575,\nCVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31580,\nCVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584,\nCVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588,\nCVE-2026-31590, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596,\nCVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31602,\nCVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606,\nCVE-2026-31607, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612,\nCVE-2026-31613, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617,\nCVE-2026-31618, CVE-2026-31619, CVE-2026-31622, CVE-2026-31623,\nCVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627,\nCVE-2026-31628, CVE-2026-31629, CVE-2026-31634, CVE-2026-31637,\nCVE-2026-31638, CVE-2026-31639, CVE-2026-31642, CVE-2026-31645,\nCVE-2026-31646, CVE-2026-31648, CVE-2026-31649, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31657, CVE-2026-31658,\nCVE-2026-31659, CVE-2026-31660, CVE-2026-31661, CVE-2026-31662,\nCVE-2026-31664, CVE-2026-31665, CVE-2026-31667, CVE-2026-31668,\nCVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31682, CVE-2026-31683, CVE-2026-31684, CVE-2026-31685,\nCVE-2026-31686, CVE-2026-31687, CVE-2026-31689, CVE-2026-31693,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43011,\nCVE-2026-43012, CVE-2026-43013, CVE-2026-43014, CVE-2026-43015,\nCVE-2026-43016, CVE-2026-43017, CVE-2026-43018, CVE-2026-43019,\nCVE-2026-43020, CVE-2026-43023, CVE-2026-43024, CVE-2026-43025,\nCVE-2026-43026, CVE-2026-43027, CVE-2026-43028, CVE-2026-43030,\nCVE-2026-43032, CVE-2026-43035, CVE-2026-43036, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43040, CVE-2026-43041, CVE-2026-43043,\nCVE-2026-43044, CVE-2026-43046, CVE-2026-43047, CVE-2026-43049,\nCVE-2026-43050, CVE-2026-43051, CVE-2026-43052, CVE-2026-43054,\nCVE-2026-43056, CVE-2026-43057, CVE-2026-43058, CVE-2026-43059,\nCVE-2026-43060, CVE-2026-43061, CVE-2026-43062, CVE-2026-43064,\nCVE-2026-43065, CVE-2026-43066, CVE-2026-43068, CVE-2026-43069,\nCVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43085, CVE-2026-43086,\nCVE-2026-43088, CVE-2026-43089, CVE-2026-43091, CVE-2026-43092,\nCVE-2026-43093, CVE-2026-43094, CVE-2026-43098, CVE-2026-43099,\nCVE-2026-43103, CVE-2026-43104, CVE-2026-43105, CVE-2026-43107,\nCVE-2026-43109, CVE-2026-43110, CVE-2026-43111, CVE-2026-43112,\nCVE-2026-43113, CVE-2026-43114, CVE-2026-43117, CVE-2026-43119,\nCVE-2026-43120, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43129, CVE-2026-43130, CVE-2026-43132, CVE-2026-43133,\nCVE-2026-43134, CVE-2026-43135, CVE-2026-43136, CVE-2026-43137,\nCVE-2026-43139, CVE-2026-43140, CVE-2026-43141, CVE-2026-43143,\nCVE-2026-43145, CVE-2026-43147, CVE-2026-43148, CVE-2026-43149,\nCVE-2026-43150, CVE-2026-43152, CVE-2026-43153, CVE-2026-43156,\nCVE-2026-43157, CVE-2026-43158, CVE-2026-43159, CVE-2026-43162,\nCVE-2026-43163, CVE-2026-43167, CVE-2026-43168, CVE-2026-43169,\nCVE-2026-43170, CVE-2026-43171, CVE-2026-43173, CVE-2026-43175,\nCVE-2026-43180, CVE-2026-43182, CVE-2026-43183, CVE-2026-43184,\nCVE-2026-43185, CVE-2026-43186, CVE-2026-43187, CVE-2026-43189,\nCVE-2026-43190, CVE-2026-43194, CVE-2026-43196, CVE-2026-43199,\nCVE-2026-43200, CVE-2026-43201, CVE-2026-43202, CVE-2026-43203,\nCVE-2026-43205, CVE-2026-43206, CVE-2026-43207, CVE-2026-43209,\nCVE-2026-43211, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43261,\nCVE-2026-43262, CVE-2026-43264, CVE-2026-43265, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43281, CVE-2026-43283, CVE-2026-43287,\nCVE-2026-43288, CVE-2026-43289, CVE-2026-43291, CVE-2026-43295,\nCVE-2026-43296, CVE-2026-43297, CVE-2026-43300, CVE-2026-43302,\nCVE-2026-43304, CVE-2026-43312, CVE-2026-43313, CVE-2026-43314,\nCVE-2026-43315, CVE-2026-43316, CVE-2026-43317, CVE-2026-43318,\nCVE-2026-43319, CVE-2026-43320, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43341, CVE-2026-43342,\nCVE-2026-43343, CVE-2026-43345, CVE-2026-43350, CVE-2026-43355,\nCVE-2026-43357, CVE-2026-43359, CVE-2026-43360, CVE-2026-43361,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43372, CVE-2026-43373, CVE-2026-43377,\nCVE-2026-43378, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43383, CVE-2026-43384, CVE-2026-43386, CVE-2026-43387,\nCVE-2026-43395, CVE-2026-43397, CVE-2026-43405, CVE-2026-43406,\nCVE-2026-43407, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43414, CVE-2026-43415,\nCVE-2026-43419, CVE-2026-43420, CVE-2026-43421, CVE-2026-43424,\nCVE-2026-43425, CVE-2026-43426, CVE-2026-43427, CVE-2026-43428,\nCVE-2026-43429, CVE-2026-43430, CVE-2026-43432, CVE-2026-43436,\nCVE-2026-43437, CVE-2026-43439, CVE-2026-43441, CVE-2026-43445,\nCVE-2026-43448, CVE-2026-43449, CVE-2026-43450, CVE-2026-43451,\nCVE-2026-43452, CVE-2026-43453, CVE-2026-43455, CVE-2026-43456,\nCVE-2026-43457, CVE-2026-43458, CVE-2026-43459, CVE-2026-43466,\nCVE-2026-43467, CVE-2026-43468, CVE-2026-43469, CVE-2026-43471,\nCVE-2026-43472, CVE-2026-43473, CVE-2026-43475, CVE-2026-43476,\nCVE-2026-43480, CVE-2026-43483, CVE-2026-43484, CVE-2026-43488,\nCVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493,\nCVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43499,\nCVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835,\nCVE-2026-45836, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840,\nCVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844,\nCVE-2026-45845, CVE-2026-45846, CVE-2026-45847, CVE-2026-45848,\nCVE-2026-45849, CVE-2026-45851, CVE-2026-45852, CVE-2026-45855,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45858, CVE-2026-45859,\nCVE-2026-45860, CVE-2026-45861, CVE-2026-45862, CVE-2026-45864,\nCVE-2026-45865, CVE-2026-45866, CVE-2026-45867, CVE-2026-45868,\nCVE-2026-45869, CVE-2026-45870, CVE-2026-45871, CVE-2026-45872,\nCVE-2026-45873, CVE-2026-45875, CVE-2026-45877, CVE-2026-45878,\nCVE-2026-45879, CVE-2026-45880, CVE-2026-45881, CVE-2026-45882,\nCVE-2026-45883, CVE-2026-45884, CVE-2026-45885, CVE-2026-45886,\nCVE-2026-45890, CVE-2026-45891, CVE-2026-45893, CVE-2026-45895,\nCVE-2026-45899, CVE-2026-45902, CVE-2026-45904, CVE-2026-45905,\nCVE-2026-45910, CVE-2026-45911, CVE-2026-45912, CVE-2026-45913,\nCVE-2026-45914, CVE-2026-45915, CVE-2026-45916, CVE-2026-45917,\nCVE-2026-45919, CVE-2026-45920, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45924, CVE-2026-45928, CVE-2026-45935, CVE-2026-45936,\nCVE-2026-45938, CVE-2026-45941, CVE-2026-45942, CVE-2026-45943,\nCVE-2026-45946, CVE-2026-45947, CVE-2026-45948, CVE-2026-45954,\nCVE-2026-45956, CVE-2026-45957, CVE-2026-45958, CVE-2026-45960,\nCVE-2026-45962, CVE-2026-45964, CVE-2026-45965, CVE-2026-45968,\nCVE-2026-45969, CVE-2026-45970, CVE-2026-45972, CVE-2026-45973,\nCVE-2026-45974, CVE-2026-45976, CVE-2026-45978, CVE-2026-45981,\nCVE-2026-45982, CVE-2026-45983, CVE-2026-45984, CVE-2026-45985,\nCVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989,\nCVE-2026-45991, CVE-2026-45994, CVE-2026-45996, CVE-2026-45997,\nCVE-2026-45999, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004,\nCVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46009,\nCVE-2026-46011, CVE-2026-46012, CVE-2026-46015, CVE-2026-46016,\nCVE-2026-46018, CVE-2026-46019, CVE-2026-46021, CVE-2026-46022,\nCVE-2026-46023, CVE-2026-46024, CVE-2026-46026, CVE-2026-46027,\nCVE-2026-46031, CVE-2026-46033, CVE-2026-46037, CVE-2026-46038,\nCVE-2026-46040, CVE-2026-46041, CVE-2026-46043, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46119,\nCVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123,\nCVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127,\nCVE-2026-46128, CVE-2026-46129, CVE-2026-46131, CVE-2026-46132,\nCVE-2026-46133, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137,\nCVE-2026-46138, CVE-2026-46139, CVE-2026-46142, CVE-2026-46143,\nCVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46149,\nCVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46157,\nCVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46163,\nCVE-2026-46164, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169,\nCVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46176,\nCVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180,\nCVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197,\nCVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201,\nCVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207,\nCVE-2026-46208, CVE-2026-46209, CVE-2026-46211, CVE-2026-46212,\nCVE-2026-46214, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220,\nCVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46229,\nCVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233,\nCVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238,\nCVE-2026-46241, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46260, CVE-2026-46261, CVE-2026-46265, CVE-2026-46266,\nCVE-2026-46267, CVE-2026-46270, CVE-2026-46273, CVE-2026-46274,\nCVE-2026-46280, CVE-2026-46282, CVE-2026-46285, CVE-2026-46286,\nCVE-2026-46287, CVE-2026-46289, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-46328, CVE-2026-52911, CVE-2026-52920, CVE-2026-52925,\nCVE-2026-52933, CVE-2026-52936, CVE-2026-52951, CVE-2026-52954,\nCVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961,\nCVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52967,\nCVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52974,\nCVE-2026-52975, CVE-2026-52977, CVE-2026-52981, CVE-2026-52982,\nCVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52989,\nCVE-2026-52990, CVE-2026-52992, CVE-2026-52993, CVE-2026-52995,\nCVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002,\nCVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53011,\nCVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015,\nCVE-2026-53016, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023,\nCVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035,\nCVE-2026-53036, CVE-2026-53037, CVE-2026-53039, CVE-2026-53040,\nCVE-2026-53041, CVE-2026-53043, CVE-2026-53045, CVE-2026-53046,\nCVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050,\nCVE-2026-53052, CVE-2026-53056, CVE-2026-53058, CVE-2026-53059,\nCVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063,\nCVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53068,\nCVE-2026-53069, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073,\nCVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077,\nCVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085,\nCVE-2026-53086, CVE-2026-53088, CVE-2026-53093, CVE-2026-53094,\nCVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53110,\nCVE-2026-53111, CVE-2026-53112, CVE-2026-53115, CVE-2026-53117,\nCVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128,\nCVE-2026-53130, CVE-2026-53279, CVE-2026-53287, CVE-2026-53289,\nCVE-2026-53291, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295,\nCVE-2026-53296, CVE-2026-53303, CVE-2026-53304, CVE-2026-53306,\nCVE-2026-53309, CVE-2026-53314, CVE-2026-53320, CVE-2026-53369,\nCVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53379,\nCVE-2026-63838, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845,\nCVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63851,\nCVE-2026-63852, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856,\nCVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63865,\nCVE-2026-64018, CVE-2026-64034, CVE-2026-64164)\n","status":"published","published":"2026-07-24T10:26:03Z","modified":"2026-11-07T01:45:29.525006235Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8619-1","title":"linux-hwe-6.8 vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - MediaTek SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IPv6 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - Kernel kexec() syscall;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - RCU subsystem;\n  - Scheduler infrastructure;\n  - Cryptographic library;\n  - Scatterlist API;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - AppArmor security module;\n  - Landlock security;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40005, CVE-2025-40135, CVE-2025-40150, CVE-2025-68175,\nCVE-2025-68239, CVE-2025-68334, CVE-2025-68736, CVE-2025-71152,\nCVE-2025-71161, CVE-2025-71203, CVE-2025-71221, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71269,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71287, CVE-2025-71288, CVE-2025-71291, CVE-2025-71292,\nCVE-2025-71294, CVE-2025-71295, CVE-2025-71297, CVE-2025-71304,\nCVE-2025-71305, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23100, CVE-2026-23104,\nCVE-2026-23118, CVE-2026-23138, CVE-2026-23154, CVE-2026-23157,\nCVE-2026-23169, CVE-2026-23171, CVE-2026-23207, CVE-2026-23220,\nCVE-2026-23221, CVE-2026-23222, CVE-2026-23226, CVE-2026-23227,\nCVE-2026-23228, CVE-2026-23229, CVE-2026-23230, CVE-2026-23233,\nCVE-2026-23234, CVE-2026-23235, CVE-2026-23236, CVE-2026-23237,\nCVE-2026-23238, CVE-2026-23241, CVE-2026-23242, CVE-2026-23243,\nCVE-2026-23244, CVE-2026-23245, CVE-2026-23246, CVE-2026-23249,\nCVE-2026-23253, CVE-2026-23255, CVE-2026-23266, CVE-2026-23267,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23272, CVE-2026-23276,\nCVE-2026-23277, CVE-2026-23278, CVE-2026-23279, CVE-2026-23281,\nCVE-2026-23284, CVE-2026-23285, CVE-2026-23286, CVE-2026-23287,\nCVE-2026-23289, CVE-2026-23290, CVE-2026-23291, CVE-2026-23292,\nCVE-2026-23293, CVE-2026-23296, CVE-2026-23298, CVE-2026-23300,\nCVE-2026-23302, CVE-2026-23303, CVE-2026-23304, CVE-2026-23306,\nCVE-2026-23307, CVE-2026-23308, CVE-2026-23310, CVE-2026-23312,\nCVE-2026-23313, CVE-2026-23315, CVE-2026-23317, CVE-2026-23318,\nCVE-2026-23319, CVE-2026-23321, CVE-2026-23324, CVE-2026-23325,\nCVE-2026-23330, CVE-2026-23334, CVE-2026-23335, CVE-2026-23336,\nCVE-2026-23339, CVE-2026-23340, CVE-2026-23343, CVE-2026-23347,\nCVE-2026-23352, CVE-2026-23356, CVE-2026-23357, CVE-2026-23359,\nCVE-2026-23360, CVE-2026-23361, CVE-2026-23362, CVE-2026-23363,\nCVE-2026-23364, CVE-2026-23365, CVE-2026-23367, CVE-2026-23368,\nCVE-2026-23369, CVE-2026-23370, CVE-2026-23372, CVE-2026-23374,\nCVE-2026-23375, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381,\nCVE-2026-23382, CVE-2026-23383, CVE-2026-23386, CVE-2026-23387,\nCVE-2026-23388, CVE-2026-23389, CVE-2026-23391, CVE-2026-23392,\nCVE-2026-23395, CVE-2026-23396, CVE-2026-23397, CVE-2026-23398,\nCVE-2026-23399, CVE-2026-23401, CVE-2026-23412, CVE-2026-23413,\nCVE-2026-23414, CVE-2026-23418, CVE-2026-23419, CVE-2026-23420,\nCVE-2026-23426, CVE-2026-23428, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454,\nCVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458,\nCVE-2026-23460, CVE-2026-23461, CVE-2026-23462, CVE-2026-23463,\nCVE-2026-23464, CVE-2026-23465, CVE-2026-23468, CVE-2026-23470,\nCVE-2026-23474, CVE-2026-23475, CVE-2026-31389, CVE-2026-31391,\nCVE-2026-31392, CVE-2026-31393, CVE-2026-31394, CVE-2026-31396,\nCVE-2026-31399, CVE-2026-31400, CVE-2026-31402, CVE-2026-31403,\nCVE-2026-31405, CVE-2026-31407, CVE-2026-31408, CVE-2026-31409,\nCVE-2026-31411, CVE-2026-31412, CVE-2026-31414, CVE-2026-31415,\nCVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31436, CVE-2026-31438, CVE-2026-31439, CVE-2026-31440,\nCVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448,\nCVE-2026-31449, CVE-2026-31450, CVE-2026-31451, CVE-2026-31452,\nCVE-2026-31453, CVE-2026-31454, CVE-2026-31455, CVE-2026-31458,\nCVE-2026-31464, CVE-2026-31466, CVE-2026-31467, CVE-2026-31469,\nCVE-2026-31470, CVE-2026-31473, CVE-2026-31474, CVE-2026-31476,\nCVE-2026-31477, CVE-2026-31478, CVE-2026-31480, CVE-2026-31482,\nCVE-2026-31483, CVE-2026-31485, CVE-2026-31487, CVE-2026-31488,\nCVE-2026-31489, CVE-2026-31492, CVE-2026-31494, CVE-2026-31495,\nCVE-2026-31496, CVE-2026-31497, CVE-2026-31498, CVE-2026-31499,\nCVE-2026-31500, CVE-2026-31502, CVE-2026-31503, CVE-2026-31505,\nCVE-2026-31506, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607,\nCVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613,\nCVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618,\nCVE-2026-31619, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624,\nCVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628,\nCVE-2026-31629, CVE-2026-31634, CVE-2026-31637, CVE-2026-31638,\nCVE-2026-31639, CVE-2026-31642, CVE-2026-31645, CVE-2026-31646,\nCVE-2026-31648, CVE-2026-31649, CVE-2026-31651, CVE-2026-31655,\nCVE-2026-31656, CVE-2026-31657, CVE-2026-31658, CVE-2026-31659,\nCVE-2026-31660, CVE-2026-31661, CVE-2026-31662, CVE-2026-31664,\nCVE-2026-31665, CVE-2026-31667, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31670, CVE-2026-31671, CVE-2026-31672, CVE-2026-31673,\nCVE-2026-31674, CVE-2026-31675, CVE-2026-31677, CVE-2026-31678,\nCVE-2026-31679, CVE-2026-31680, CVE-2026-31681, CVE-2026-31682,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31685, CVE-2026-31686,\nCVE-2026-31687, CVE-2026-31689, CVE-2026-31693, CVE-2026-31694,\nCVE-2026-31695, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698,\nCVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702,\nCVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707,\nCVE-2026-31708, CVE-2026-31709, CVE-2026-31711, CVE-2026-31712,\nCVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31720,\nCVE-2026-31721, CVE-2026-31722, CVE-2026-31723, CVE-2026-31724,\nCVE-2026-31725, CVE-2026-31726, CVE-2026-31728, CVE-2026-31729,\nCVE-2026-31730, CVE-2026-31731, CVE-2026-31737, CVE-2026-31738,\nCVE-2026-31740, CVE-2026-31741, CVE-2026-31747, CVE-2026-31748,\nCVE-2026-31749, CVE-2026-31751, CVE-2026-31752, CVE-2026-31754,\nCVE-2026-31755, CVE-2026-31756, CVE-2026-31758, CVE-2026-31759,\nCVE-2026-31761, CVE-2026-31762, CVE-2026-31763, CVE-2026-31767,\nCVE-2026-31768, CVE-2026-31770, CVE-2026-31772, CVE-2026-31773,\nCVE-2026-31778, CVE-2026-31779, CVE-2026-31780, CVE-2026-31781,\nCVE-2026-31788, CVE-2026-43007, CVE-2026-43011, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43040, CVE-2026-43041, CVE-2026-43043, CVE-2026-43044,\nCVE-2026-43046, CVE-2026-43047, CVE-2026-43049, CVE-2026-43050,\nCVE-2026-43051, CVE-2026-43052, CVE-2026-43054, CVE-2026-43056,\nCVE-2026-43057, CVE-2026-43058, CVE-2026-43059, CVE-2026-43060,\nCVE-2026-43061, CVE-2026-43062, CVE-2026-43064, CVE-2026-43065,\nCVE-2026-43066, CVE-2026-43068, CVE-2026-43069, CVE-2026-43071,\nCVE-2026-43072, CVE-2026-43073, CVE-2026-43074, CVE-2026-43075,\nCVE-2026-43076, CVE-2026-43079, CVE-2026-43080, CVE-2026-43081,\nCVE-2026-43082, CVE-2026-43085, CVE-2026-43086, CVE-2026-43088,\nCVE-2026-43089, CVE-2026-43091, CVE-2026-43092, CVE-2026-43093,\nCVE-2026-43094, CVE-2026-43098, CVE-2026-43099, CVE-2026-43103,\nCVE-2026-43104, CVE-2026-43105, CVE-2026-43107, CVE-2026-43109,\nCVE-2026-43110, CVE-2026-43111, CVE-2026-43112, CVE-2026-43113,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43123, CVE-2026-43124, CVE-2026-43128, CVE-2026-43129,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43162, CVE-2026-43163,\nCVE-2026-43167, CVE-2026-43168, CVE-2026-43169, CVE-2026-43170,\nCVE-2026-43171, CVE-2026-43173, CVE-2026-43175, CVE-2026-43180,\nCVE-2026-43182, CVE-2026-43183, CVE-2026-43184, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43187, CVE-2026-43189, CVE-2026-43190,\nCVE-2026-43194, CVE-2026-43196, CVE-2026-43199, CVE-2026-43200,\nCVE-2026-43201, CVE-2026-43202, CVE-2026-43203, CVE-2026-43205,\nCVE-2026-43206, CVE-2026-43207, CVE-2026-43209, CVE-2026-43211,\nCVE-2026-43212, CVE-2026-43214, CVE-2026-43215, CVE-2026-43218,\nCVE-2026-43221, CVE-2026-43222, CVE-2026-43223, CVE-2026-43225,\nCVE-2026-43226, CVE-2026-43227, CVE-2026-43230, CVE-2026-43231,\nCVE-2026-43232, CVE-2026-43233, CVE-2026-43236, CVE-2026-43238,\nCVE-2026-43239, CVE-2026-43241, CVE-2026-43242, CVE-2026-43244,\nCVE-2026-43245, CVE-2026-43246, CVE-2026-43248, CVE-2026-43249,\nCVE-2026-43250, CVE-2026-43251, CVE-2026-43252, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43265,\nCVE-2026-43266, CVE-2026-43268, CVE-2026-43269, CVE-2026-43270,\nCVE-2026-43271, CVE-2026-43273, CVE-2026-43275, CVE-2026-43277,\nCVE-2026-43278, CVE-2026-43279, CVE-2026-43281, CVE-2026-43283,\nCVE-2026-43287, CVE-2026-43288, CVE-2026-43289, CVE-2026-43291,\nCVE-2026-43295, CVE-2026-43296, CVE-2026-43297, CVE-2026-43300,\nCVE-2026-43302, CVE-2026-43304, CVE-2026-43312, CVE-2026-43313,\nCVE-2026-43314, CVE-2026-43315, CVE-2026-43316, CVE-2026-43317,\nCVE-2026-43318, CVE-2026-43319, CVE-2026-43320, CVE-2026-43324,\nCVE-2026-43327, CVE-2026-43328, CVE-2026-43329, CVE-2026-43330,\nCVE-2026-43332, CVE-2026-43333, CVE-2026-43334, CVE-2026-43336,\nCVE-2026-43338, CVE-2026-43339, CVE-2026-43340, CVE-2026-43341,\nCVE-2026-43342, CVE-2026-43343, CVE-2026-43345, CVE-2026-43350,\nCVE-2026-43355, CVE-2026-43357, CVE-2026-43359, CVE-2026-43360,\nCVE-2026-43361, CVE-2026-43362, CVE-2026-43363, CVE-2026-43365,\nCVE-2026-43366, CVE-2026-43368, CVE-2026-43370, CVE-2026-43372,\nCVE-2026-43373, CVE-2026-43377, CVE-2026-43378, CVE-2026-43380,\nCVE-2026-43381, CVE-2026-43382, CVE-2026-43383, CVE-2026-43384,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43406, CVE-2026-43407, CVE-2026-43408,\nCVE-2026-43409, CVE-2026-43411, CVE-2026-43412, CVE-2026-43413,\nCVE-2026-43414, CVE-2026-43415, CVE-2026-43419, CVE-2026-43420,\nCVE-2026-43421, CVE-2026-43424, CVE-2026-43425, CVE-2026-43426,\nCVE-2026-43427, CVE-2026-43428, CVE-2026-43429, CVE-2026-43430,\nCVE-2026-43432, CVE-2026-43436, CVE-2026-43437, CVE-2026-43439,\nCVE-2026-43441, CVE-2026-43445, CVE-2026-43448, CVE-2026-43449,\nCVE-2026-43450, CVE-2026-43451, CVE-2026-43452, CVE-2026-43453,\nCVE-2026-43455, CVE-2026-43456, CVE-2026-43457, CVE-2026-43458,\nCVE-2026-43459, CVE-2026-43466, CVE-2026-43467, CVE-2026-43468,\nCVE-2026-43469, CVE-2026-43471, CVE-2026-43472, CVE-2026-43473,\nCVE-2026-43475, CVE-2026-43476, CVE-2026-43480, CVE-2026-43483,\nCVE-2026-43484, CVE-2026-43488, CVE-2026-43490, CVE-2026-43491,\nCVE-2026-43492, CVE-2026-43493, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43501, CVE-2026-43502,\nCVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45838,\nCVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842,\nCVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846,\nCVE-2026-45847, CVE-2026-45848, CVE-2026-45849, CVE-2026-45851,\nCVE-2026-45852, CVE-2026-45855, CVE-2026-45856, CVE-2026-45857,\nCVE-2026-45858, CVE-2026-45859, CVE-2026-45860, CVE-2026-45861,\nCVE-2026-45862, CVE-2026-45864, CVE-2026-45865, CVE-2026-45866,\nCVE-2026-45867, CVE-2026-45868, CVE-2026-45869, CVE-2026-45870,\nCVE-2026-45871, CVE-2026-45872, CVE-2026-45873, CVE-2026-45875,\nCVE-2026-45877, CVE-2026-45878, CVE-2026-45879, CVE-2026-45880,\nCVE-2026-45881, CVE-2026-45882, CVE-2026-45883, CVE-2026-45884,\nCVE-2026-45885, CVE-2026-45886, CVE-2026-45890, CVE-2026-45891,\nCVE-2026-45893, CVE-2026-45895, CVE-2026-45899, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45911,\nCVE-2026-45912, CVE-2026-45913, CVE-2026-45914, CVE-2026-45915,\nCVE-2026-45916, CVE-2026-45917, CVE-2026-45919, CVE-2026-45920,\nCVE-2026-45921, CVE-2026-45923, CVE-2026-45924, CVE-2026-45928,\nCVE-2026-45935, CVE-2026-45936, CVE-2026-45938, CVE-2026-45941,\nCVE-2026-45942, CVE-2026-45943, CVE-2026-45946, CVE-2026-45947,\nCVE-2026-45948, CVE-2026-45954, CVE-2026-45956, CVE-2026-45957,\nCVE-2026-45958, CVE-2026-45960, CVE-2026-45962, CVE-2026-45964,\nCVE-2026-45965, CVE-2026-45968, CVE-2026-45969, CVE-2026-45970,\nCVE-2026-45972, CVE-2026-45973, CVE-2026-45974, CVE-2026-45976,\nCVE-2026-45978, CVE-2026-45981, CVE-2026-45982, CVE-2026-45983,\nCVE-2026-45984, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45988, CVE-2026-45989, CVE-2026-45991, CVE-2026-45994,\nCVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46002,\nCVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006,\nCVE-2026-46007, CVE-2026-46009, CVE-2026-46011, CVE-2026-46012,\nCVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019,\nCVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024,\nCVE-2026-46026, CVE-2026-46027, CVE-2026-46031, CVE-2026-46033,\nCVE-2026-46037, CVE-2026-46038, CVE-2026-46040, CVE-2026-46041,\nCVE-2026-46043, CVE-2026-46044, CVE-2026-46046, CVE-2026-46047,\nCVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052,\nCVE-2026-46053, CVE-2026-46056, CVE-2026-46058, CVE-2026-46061,\nCVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065,\nCVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46072,\nCVE-2026-46073, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077,\nCVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46082,\nCVE-2026-46083, CVE-2026-46084, CVE-2026-46086, CVE-2026-46088,\nCVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092,\nCVE-2026-46094, CVE-2026-46098, CVE-2026-46099, CVE-2026-46101,\nCVE-2026-46102, CVE-2026-46103, CVE-2026-46106, CVE-2026-46107,\nCVE-2026-46108, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112,\nCVE-2026-46113, CVE-2026-46114, CVE-2026-46115, CVE-2026-46116,\nCVE-2026-46117, CVE-2026-46119, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46135,\nCVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139,\nCVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145,\nCVE-2026-46146, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151,\nCVE-2026-46152, CVE-2026-46157, CVE-2026-46159, CVE-2026-46160,\nCVE-2026-46161, CVE-2026-46163, CVE-2026-46164, CVE-2026-46167,\nCVE-2026-46168, CVE-2026-46169, CVE-2026-46172, CVE-2026-46173,\nCVE-2026-46174, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178,\nCVE-2026-46179, CVE-2026-46180, CVE-2026-46184, CVE-2026-46185,\nCVE-2026-46186, CVE-2026-46187, CVE-2026-46189, CVE-2026-46190,\nCVE-2026-46191, CVE-2026-46193, CVE-2026-46194, CVE-2026-46195,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46243,\nCVE-2026-46244, CVE-2026-46246, CVE-2026-46247, CVE-2026-46249,\nCVE-2026-46250, CVE-2026-46251, CVE-2026-46253, CVE-2026-46254,\nCVE-2026-46255, CVE-2026-46259, CVE-2026-46260, CVE-2026-46261,\nCVE-2026-46265, CVE-2026-46266, CVE-2026-46267, CVE-2026-46270,\nCVE-2026-46273, CVE-2026-46274, CVE-2026-46280, CVE-2026-46282,\nCVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46289,\nCVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294,\nCVE-2026-46296, CVE-2026-46299, CVE-2026-46301, CVE-2026-46303,\nCVE-2026-46304, CVE-2026-46306, CVE-2026-46307, CVE-2026-46312,\nCVE-2026-46314, CVE-2026-46319, CVE-2026-46328, CVE-2026-52911,\nCVE-2026-52920, CVE-2026-52925, CVE-2026-52933, CVE-2026-52936,\nCVE-2026-52951, CVE-2026-52954, CVE-2026-52955, CVE-2026-52957,\nCVE-2026-52958, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963,\nCVE-2026-52964, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969,\nCVE-2026-52970, CVE-2026-52974, CVE-2026-52975, CVE-2026-52977,\nCVE-2026-52981, CVE-2026-52982, CVE-2026-52984, CVE-2026-52985,\nCVE-2026-52986, CVE-2026-52989, CVE-2026-52990, CVE-2026-52992,\nCVE-2026-52993, CVE-2026-52995, CVE-2026-52998, CVE-2026-52999,\nCVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004,\nCVE-2026-53006, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013,\nCVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53021,\nCVE-2026-53022, CVE-2026-53023, CVE-2026-53032, CVE-2026-53033,\nCVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037,\nCVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53043,\nCVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048,\nCVE-2026-53049, CVE-2026-53050, CVE-2026-53052, CVE-2026-53056,\nCVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061,\nCVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065,\nCVE-2026-53066, CVE-2026-53068, CVE-2026-53069, CVE-2026-53071,\nCVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075,\nCVE-2026-53076, CVE-2026-53077, CVE-2026-53082, CVE-2026-53083,\nCVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53088,\nCVE-2026-53093, CVE-2026-53094, CVE-2026-53096, CVE-2026-53097,\nCVE-2026-53098, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112,\nCVE-2026-53115, CVE-2026-53117, CVE-2026-53122, CVE-2026-53123,\nCVE-2026-53126, CVE-2026-53128, CVE-2026-53130, CVE-2026-53279,\nCVE-2026-53287, CVE-2026-53289, CVE-2026-53291, CVE-2026-53293,\nCVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53303,\nCVE-2026-53304, CVE-2026-53306, CVE-2026-53309, CVE-2026-53314,\nCVE-2026-53320, CVE-2026-53369, CVE-2026-53374, CVE-2026-53375,\nCVE-2026-53376, CVE-2026-53379, CVE-2026-63838, CVE-2026-63843,\nCVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847,\nCVE-2026-63848, CVE-2026-63851, CVE-2026-63852, CVE-2026-63854,\nCVE-2026-63855, CVE-2026-63856, CVE-2026-63860, CVE-2026-63861,\nCVE-2026-63862, CVE-2026-63865)\n","status":"published","published":"2026-07-28T07:28:45Z","modified":"2026-11-07T01:45:56.683802514Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8665-1","title":"linux-raspi, linux-raspi-realtime vulnerabilities","description":"It was discovered that some AMD processors did not properly clear data in\nthe floating point divider unit during speculative execution. A local\nattacker could use this to expose sensitive information. (CVE-2025-54505)\n\nIt was discovered that some AMD Zen 2 processors did not properly isolate\nshared resources in the operation cache. A local attacker could possibly\nuse this issue to corrupt instructions executed at a higher privilege\nlevel, resulting in privilege escalation. (CVE-2025-54518)\n\nIt was discovered that some AMD Zen 5 processors supporting RDSEED\ninstruction did not properly handle entropy, potentially resulting in the\nconsumption of insufficiently random values. A local attacker could\npossibly use this issue to influence the values returned by the RDSEED\ninstruction causing loss of confidentiality and integrity. (CVE-2025-62626)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - Drivers core;\n  - Power management core;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Rados block device (RBD) driver;\n  - Compressed RAM block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - EFI core;\n  - GPU drivers;\n  - Greybus drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IRQ chip drivers;\n  - LED subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - MediaTek SMI driver;\n  - NVIDIA Tegra memory controller driver;\n  - Fastrpc Driver;\n  - IBM Advanced System Management driver;\n  - MMC subsystem;\n  - MTD block device drivers;\n  - Network drivers;\n  - Ethernet bonding driver;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - Near Field Communication (NFC) drivers;\n  - NTB driver;\n  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PCI subsystem;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - Broadcom BCM2835 power domain driver;\n  - Generic PM domains;\n  - i.MX PM domains;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Freescale SoC drivers;\n  - Microchip PolarFire SoC system controller driver;\n  - SPI subsystem;\n  - Media staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - SM750 framebuffer staging driver;\n  - TCM subsystem;\n  - Thermal drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Cadence USB3 driver;\n  - USB Device Class drivers;\n  - ULPI bus;\n  - USB core drivers;\n  - DesignWare USB2 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Mustek MDC800 USB digital camera driver;\n  - USB YUREX driver;\n  - Renesas USBHS Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Framebuffer layer;\n  - TSM TDX Guest driver;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - Network file systems library;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - Tracing file system;\n  - UDF file system;\n  - XFS file system;\n  - Kernel CPU control infrastructure;\n  - QorIQ DPAA2 FSL-MC bus driver;\n  - Memory Management;\n  - Integrity Measurement Architecture(IMA) framework;\n  - KVM subsystem;\n  - Memory management;\n  - Networking core;\n  - padata parallel execution mechanism;\n  - PPP protocol drivers and compressors;\n  - Linux Security Modules (LSM) Framework;\n  - Tracing infrastructure;\n  - Network traffic control;\n  - Distributed Switch Architecture;\n  - IPv4 networking;\n  - IP tunnels definitions;\n  - MAC80211 subsystem;\n  - Netfilter;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Audit subsystem;\n  - BPF subsystem;\n  - Control group (cgroup);\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel fork() syscall;\n  - Kernel futex primitives;\n  - KProbes tracing;\n  - Locking primitives;\n  - Kernel module support;\n  - Padata parallel execution mechanism;\n  - Cryptographic library;\n  - Heterogeneous memory management;\n  - KASAN memory debugging framework;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - IPv6 networking;\n  - XFRM subsystem;\n  - L2TP protocol;\n  - Management Component Transport Protocol (MCTP);\n  - Multipath TCP;\n  - NCSI (Network Controller Sideband Interface) driver;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Packet sockets;\n  - Qualcomm IPC Router (QRTR);\n  - RDS protocol;\n  - RF switch subsystem;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - Stream parser;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - eXpress Data Path;\n  - Landlock security;\n  - ALSA framework;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - QCOM ASoC drivers;\n  - Renesas ASoC drivers;\n  - Samsung ASoC drivers;\n  - SoC audio core drivers;\n  - SOF drivers;\n  - STI ASoC drivers;\n  - USB sound devices;\n  - Objtool;\n(CVE-2025-21709, CVE-2025-22116, CVE-2025-38426, CVE-2025-39764,\nCVE-2025-40135, CVE-2025-40150, CVE-2025-68175, CVE-2025-68239,\nCVE-2025-68334, CVE-2025-68736, CVE-2025-71152, CVE-2025-71161,\nCVE-2025-71203, CVE-2025-71221, CVE-2025-71269, CVE-2025-71287,\nCVE-2025-71288, CVE-2026-22981, CVE-2026-22985, CVE-2026-22993,\nCVE-2026-23004, CVE-2026-23066, CVE-2026-23104, CVE-2026-23118,\nCVE-2026-23138, CVE-2026-23154, CVE-2026-23157, CVE-2026-23171,\nCVE-2026-23207, CVE-2026-23226, CVE-2026-23227, CVE-2026-23244,\nCVE-2026-23245, CVE-2026-23246, CVE-2026-23253, CVE-2026-23255,\nCVE-2026-23270, CVE-2026-23271, CVE-2026-23276, CVE-2026-23277,\nCVE-2026-23279, CVE-2026-23281, CVE-2026-23284, CVE-2026-23285,\nCVE-2026-23286, CVE-2026-23287, CVE-2026-23289, CVE-2026-23290,\nCVE-2026-23291, CVE-2026-23292, CVE-2026-23293, CVE-2026-23296,\nCVE-2026-23298, CVE-2026-23300, CVE-2026-23302, CVE-2026-23303,\nCVE-2026-23304, CVE-2026-23306, CVE-2026-23307, CVE-2026-23308,\nCVE-2026-23310, CVE-2026-23312, CVE-2026-23313, CVE-2026-23315,\nCVE-2026-23317, CVE-2026-23318, CVE-2026-23319, CVE-2026-23321,\nCVE-2026-23324, CVE-2026-23325, CVE-2026-23330, CVE-2026-23334,\nCVE-2026-23335, CVE-2026-23336, CVE-2026-23339, CVE-2026-23340,\nCVE-2026-23343, CVE-2026-23347, CVE-2026-23352, CVE-2026-23356,\nCVE-2026-23357, CVE-2026-23359, CVE-2026-23360, CVE-2026-23361,\nCVE-2026-23362, CVE-2026-23363, CVE-2026-23364, CVE-2026-23365,\nCVE-2026-23367, CVE-2026-23368, CVE-2026-23369, CVE-2026-23370,\nCVE-2026-23372, CVE-2026-23374, CVE-2026-23375, CVE-2026-23378,\nCVE-2026-23379, CVE-2026-23381, CVE-2026-23382, CVE-2026-23383,\nCVE-2026-23386, CVE-2026-23387, CVE-2026-23388, CVE-2026-23389,\nCVE-2026-23391, CVE-2026-23395, CVE-2026-23396, CVE-2026-23397,\nCVE-2026-23398, CVE-2026-23399, CVE-2026-23401, CVE-2026-23412,\nCVE-2026-23413, CVE-2026-23414, CVE-2026-23418, CVE-2026-23419,\nCVE-2026-23420, CVE-2026-23426, CVE-2026-23434, CVE-2026-23438,\nCVE-2026-23439, CVE-2026-23440, CVE-2026-23441, CVE-2026-23442,\nCVE-2026-23444, CVE-2026-23446, CVE-2026-23447, CVE-2026-23448,\nCVE-2026-23449, CVE-2026-23452, CVE-2026-23454, CVE-2026-23456,\nCVE-2026-23457, CVE-2026-23458, CVE-2026-23460, CVE-2026-23461,\nCVE-2026-23462, CVE-2026-23463, CVE-2026-23464, CVE-2026-23465,\nCVE-2026-23468, CVE-2026-23470, CVE-2026-23474, CVE-2026-23475,\nCVE-2026-31389, CVE-2026-31391, CVE-2026-31392, CVE-2026-31393,\nCVE-2026-31394, CVE-2026-31396, CVE-2026-31399, CVE-2026-31400,\nCVE-2026-31403, CVE-2026-31405, CVE-2026-31407, CVE-2026-31408,\nCVE-2026-31409, CVE-2026-31412, CVE-2026-31413, CVE-2026-31414,\nCVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31421,\nCVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31425,\nCVE-2026-31426, CVE-2026-31427, CVE-2026-31428, CVE-2026-31429,\nCVE-2026-31430, CVE-2026-31432, CVE-2026-31433, CVE-2026-31434,\nCVE-2026-31438, CVE-2026-31439, CVE-2026-31440, CVE-2026-31441,\nCVE-2026-31446, CVE-2026-31447, CVE-2026-31449, CVE-2026-31450,\nCVE-2026-31451, CVE-2026-31452, CVE-2026-31453, CVE-2026-31454,\nCVE-2026-31455, CVE-2026-31458, CVE-2026-31464, CVE-2026-31466,\nCVE-2026-31467, CVE-2026-31469, CVE-2026-31470, CVE-2026-31473,\nCVE-2026-31474, CVE-2026-31476, CVE-2026-31477, CVE-2026-31480,\nCVE-2026-31482, CVE-2026-31483, CVE-2026-31485, CVE-2026-31487,\nCVE-2026-31488, CVE-2026-31489, CVE-2026-31492, CVE-2026-31494,\nCVE-2026-31495, CVE-2026-31496, CVE-2026-31497, CVE-2026-31498,\nCVE-2026-31499, CVE-2026-31500, CVE-2026-31502, CVE-2026-31503,\nCVE-2026-31505, CVE-2026-31507, CVE-2026-31508, CVE-2026-31509,\nCVE-2026-31510, CVE-2026-31511, CVE-2026-31512, CVE-2026-31515,\nCVE-2026-31516, CVE-2026-31518, CVE-2026-31519, CVE-2026-31520,\nCVE-2026-31521, CVE-2026-31522, CVE-2026-31523, CVE-2026-31524,\nCVE-2026-31525, CVE-2026-31527, CVE-2026-31528, CVE-2026-31530,\nCVE-2026-31532, CVE-2026-31540, CVE-2026-31542, CVE-2026-31545,\nCVE-2026-31546, CVE-2026-31548, CVE-2026-31549, CVE-2026-31550,\nCVE-2026-31551, CVE-2026-31552, CVE-2026-31554, CVE-2026-31555,\nCVE-2026-31556, CVE-2026-31557, CVE-2026-31563, CVE-2026-31565,\nCVE-2026-31566, CVE-2026-31570, CVE-2026-31575, CVE-2026-31576,\nCVE-2026-31577, CVE-2026-31578, CVE-2026-31580, CVE-2026-31581,\nCVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585,\nCVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31590,\nCVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597,\nCVE-2026-31598, CVE-2026-31599, CVE-2026-31602, CVE-2026-31603,\nCVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31610,\nCVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31615,\nCVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619,\nCVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625,\nCVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629,\nCVE-2026-31634, CVE-2026-31638, CVE-2026-31639, CVE-2026-31642,\nCVE-2026-31645, CVE-2026-31646, CVE-2026-31648, CVE-2026-31651,\nCVE-2026-31655, CVE-2026-31656, CVE-2026-31658, CVE-2026-31660,\nCVE-2026-31661, CVE-2026-31662, CVE-2026-31664, CVE-2026-31665,\nCVE-2026-31667, CVE-2026-31670, CVE-2026-31671, CVE-2026-31672,\nCVE-2026-31673, CVE-2026-31674, CVE-2026-31675, CVE-2026-31677,\nCVE-2026-31678, CVE-2026-31679, CVE-2026-31680, CVE-2026-31681,\nCVE-2026-31683, CVE-2026-31684, CVE-2026-31686, CVE-2026-31689,\nCVE-2026-31694, CVE-2026-31695, CVE-2026-31696, CVE-2026-31697,\nCVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701,\nCVE-2026-31702, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706,\nCVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31711,\nCVE-2026-31712, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716,\nCVE-2026-31720, CVE-2026-31721, CVE-2026-31722, CVE-2026-31723,\nCVE-2026-31724, CVE-2026-31725, CVE-2026-31726, CVE-2026-31728,\nCVE-2026-31729, CVE-2026-31730, CVE-2026-31731, CVE-2026-31737,\nCVE-2026-31738, CVE-2026-31740, CVE-2026-31741, CVE-2026-31747,\nCVE-2026-31748, CVE-2026-31749, CVE-2026-31751, CVE-2026-31752,\nCVE-2026-31754, CVE-2026-31755, CVE-2026-31756, CVE-2026-31758,\nCVE-2026-31759, CVE-2026-31761, CVE-2026-31762, CVE-2026-31763,\nCVE-2026-31767, CVE-2026-31768, CVE-2026-31770, CVE-2026-31772,\nCVE-2026-31773, CVE-2026-31778, CVE-2026-31779, CVE-2026-31780,\nCVE-2026-31781, CVE-2026-31788, CVE-2026-43007, CVE-2026-43012,\nCVE-2026-43013, CVE-2026-43014, CVE-2026-43015, CVE-2026-43016,\nCVE-2026-43017, CVE-2026-43018, CVE-2026-43019, CVE-2026-43020,\nCVE-2026-43023, CVE-2026-43024, CVE-2026-43025, CVE-2026-43026,\nCVE-2026-43027, CVE-2026-43028, CVE-2026-43030, CVE-2026-43032,\nCVE-2026-43035, CVE-2026-43036, CVE-2026-43040, CVE-2026-43041,\nCVE-2026-43043, CVE-2026-43044, CVE-2026-43046, CVE-2026-43047,\nCVE-2026-43049, CVE-2026-43050, CVE-2026-43051, CVE-2026-43052,\nCVE-2026-43054, CVE-2026-43056, CVE-2026-43057, CVE-2026-43058,\nCVE-2026-43059, CVE-2026-43060, CVE-2026-43061, CVE-2026-43062,\nCVE-2026-43064, CVE-2026-43065, CVE-2026-43066, CVE-2026-43068,\nCVE-2026-43069, CVE-2026-43072, CVE-2026-43073, CVE-2026-43074,\nCVE-2026-43075, CVE-2026-43076, CVE-2026-43079, CVE-2026-43080,\nCVE-2026-43081, CVE-2026-43082, CVE-2026-43084, CVE-2026-43085,\nCVE-2026-43086, CVE-2026-43088, CVE-2026-43089, CVE-2026-43091,\nCVE-2026-43092, CVE-2026-43093, CVE-2026-43094, CVE-2026-43098,\nCVE-2026-43099, CVE-2026-43103, CVE-2026-43104, CVE-2026-43105,\nCVE-2026-43107, CVE-2026-43109, CVE-2026-43110, CVE-2026-43111,\nCVE-2026-43112, CVE-2026-43113, CVE-2026-43119, CVE-2026-43120,\nCVE-2026-43129, CVE-2026-43162, CVE-2026-43245, CVE-2026-43252,\nCVE-2026-43265, CVE-2026-43281, CVE-2026-43324, CVE-2026-43327,\nCVE-2026-43328, CVE-2026-43329, CVE-2026-43330, CVE-2026-43332,\nCVE-2026-43333, CVE-2026-43334, CVE-2026-43336, CVE-2026-43338,\nCVE-2026-43339, CVE-2026-43340, CVE-2026-43342, CVE-2026-43343,\nCVE-2026-43345, CVE-2026-43350, CVE-2026-43355, CVE-2026-43357,\nCVE-2026-43359, CVE-2026-43360, CVE-2026-43361, CVE-2026-43362,\nCVE-2026-43363, CVE-2026-43365, CVE-2026-43366, CVE-2026-43368,\nCVE-2026-43370, CVE-2026-43371, CVE-2026-43372, CVE-2026-43373,\nCVE-2026-43377, CVE-2026-43380, CVE-2026-43381, CVE-2026-43382,\nCVE-2026-43386, CVE-2026-43387, CVE-2026-43395, CVE-2026-43397,\nCVE-2026-43405, CVE-2026-43408, CVE-2026-43409, CVE-2026-43411,\nCVE-2026-43412, CVE-2026-43413, CVE-2026-43415, CVE-2026-43419,\nCVE-2026-43420, CVE-2026-43421, CVE-2026-43424, CVE-2026-43425,\nCVE-2026-43426, CVE-2026-43427, CVE-2026-43428, CVE-2026-43429,\nCVE-2026-43430, CVE-2026-43432, CVE-2026-43436, CVE-2026-43437,\nCVE-2026-43439, CVE-2026-43441, CVE-2026-43445, CVE-2026-43448,\nCVE-2026-43449, CVE-2026-43450, CVE-2026-43451, CVE-2026-43452,\nCVE-2026-43453, CVE-2026-43455, CVE-2026-43456, CVE-2026-43457,\nCVE-2026-43458, CVE-2026-43459, CVE-2026-43466, CVE-2026-43467,\nCVE-2026-43468, CVE-2026-43469, CVE-2026-43471, CVE-2026-43472,\nCVE-2026-43473, CVE-2026-43475, CVE-2026-43476, CVE-2026-43480,\nCVE-2026-43483, CVE-2026-43484, CVE-2026-43488, CVE-2026-43490,\nCVE-2026-43491, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496,\nCVE-2026-43497, CVE-2026-43499, CVE-2026-43502, CVE-2026-45834,\nCVE-2026-45835, CVE-2026-45836, CVE-2026-45838, CVE-2026-45839,\nCVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843,\nCVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45855,\nCVE-2026-45858, CVE-2026-45899, CVE-2026-45911, CVE-2026-45920,\nCVE-2026-45924, CVE-2026-45942, CVE-2026-45943, CVE-2026-45956,\nCVE-2026-45958, CVE-2026-45985, CVE-2026-45986, CVE-2026-45987,\nCVE-2026-45989, CVE-2026-45991, CVE-2026-45994, CVE-2026-45996,\nCVE-2026-45997, CVE-2026-45999, CVE-2026-46002, CVE-2026-46003,\nCVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007,\nCVE-2026-46009, CVE-2026-46011, CVE-2026-46012, CVE-2026-46015,\nCVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46021,\nCVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46026,\nCVE-2026-46027, CVE-2026-46031, CVE-2026-46033, CVE-2026-46037,\nCVE-2026-46038, CVE-2026-46040, CVE-2026-46041, CVE-2026-46044,\nCVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050,\nCVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46056,\nCVE-2026-46058, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063,\nCVE-2026-46064, CVE-2026-46065, CVE-2026-46068, CVE-2026-46069,\nCVE-2026-46070, CVE-2026-46072, CVE-2026-46073, CVE-2026-46075,\nCVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079,\nCVE-2026-46080, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084,\nCVE-2026-46086, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090,\nCVE-2026-46091, CVE-2026-46092, CVE-2026-46094, CVE-2026-46098,\nCVE-2026-46099, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103,\nCVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46110,\nCVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114,\nCVE-2026-46116, CVE-2026-46117, CVE-2026-46120, CVE-2026-46121,\nCVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125,\nCVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129,\nCVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46136,\nCVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46142,\nCVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146,\nCVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152,\nCVE-2026-46157, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161,\nCVE-2026-46163, CVE-2026-46164, CVE-2026-46167, CVE-2026-46168,\nCVE-2026-46169, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174,\nCVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179,\nCVE-2026-46180, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187,\nCVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46193,\nCVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199,\nCVE-2026-46200, CVE-2026-46201, CVE-2026-46204, CVE-2026-46205,\nCVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209,\nCVE-2026-46211, CVE-2026-46212, CVE-2026-46214, CVE-2026-46218,\nCVE-2026-46219, CVE-2026-46220, CVE-2026-46225, CVE-2026-46226,\nCVE-2026-46227, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231,\nCVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235,\nCVE-2026-46236, CVE-2026-46238, CVE-2026-46241, CVE-2026-46273,\nCVE-2026-46274, CVE-2026-46280, CVE-2026-46282, CVE-2026-46285,\nCVE-2026-46286, CVE-2026-46287, CVE-2026-46291, CVE-2026-46292,\nCVE-2026-46293, CVE-2026-46294, CVE-2026-46296, CVE-2026-46299,\nCVE-2026-46301, CVE-2026-46303, CVE-2026-46304, CVE-2026-46306,\nCVE-2026-46307, CVE-2026-46312, CVE-2026-46314, CVE-2026-46319,\nCVE-2026-52911, CVE-2026-52920, CVE-2026-52925, CVE-2026-52933,\nCVE-2026-52936, CVE-2026-52951, CVE-2026-52954, CVE-2026-52955,\nCVE-2026-52957, CVE-2026-52958, CVE-2026-52961, CVE-2026-52962,\nCVE-2026-52963, CVE-2026-52964, CVE-2026-52967, CVE-2026-52968,\nCVE-2026-52969, CVE-2026-52970, CVE-2026-52974, CVE-2026-52975,\nCVE-2026-52977, CVE-2026-52981, CVE-2026-52982, CVE-2026-52984,\nCVE-2026-52985, CVE-2026-52986, CVE-2026-52989, CVE-2026-52990,\nCVE-2026-52992, CVE-2026-52993, CVE-2026-52995, CVE-2026-52998,\nCVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003,\nCVE-2026-53004, CVE-2026-53006, CVE-2026-53011, CVE-2026-53012,\nCVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016,\nCVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53032,\nCVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036,\nCVE-2026-53037, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041,\nCVE-2026-53043, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047,\nCVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53052,\nCVE-2026-53056, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060,\nCVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064,\nCVE-2026-53065, CVE-2026-53066, CVE-2026-53068, CVE-2026-53069,\nCVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074,\nCVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53082,\nCVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086,\nCVE-2026-53088, CVE-2026-53093, CVE-2026-53094, CVE-2026-53096,\nCVE-2026-53097, CVE-2026-53098, CVE-2026-53110, CVE-2026-53111,\nCVE-2026-53112, CVE-2026-53115, CVE-2026-53117, CVE-2026-53122,\nCVE-2026-53123, CVE-2026-53126, CVE-2026-53128, CVE-2026-53130,\nCVE-2026-53279, CVE-2026-53287, CVE-2026-53289, CVE-2026-53291,\nCVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296,\nCVE-2026-53303, CVE-2026-53304, CVE-2026-53306, CVE-2026-53309,\nCVE-2026-53314, CVE-2026-53320, CVE-2026-53369, CVE-2026-53374,\nCVE-2026-53375, CVE-2026-53376, CVE-2026-53379, CVE-2026-63838,\nCVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846,\nCVE-2026-63847, CVE-2026-63848, CVE-2026-63851, CVE-2026-63852,\nCVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63860,\nCVE-2026-63861, CVE-2026-63862, CVE-2026-63865, CVE-2026-64164,\nCVE-2026-64587)\n","status":"published","published":"2026-08-20T23:31:14Z","modified":"2026-11-09T12:48:40.63232576Z","updated_at":"2026-11-07T01:56:47.245871Z"},{"id":"USN-8669-1","title":"linux-nvidia-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  - 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  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments 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  - File systems infrastructure;\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  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv4 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - TCP network protocol;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\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  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\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-31405,\nCVE-2026-31414, CVE-2026-31444, CVE-2026-31501, CVE-2026-31589,\nCVE-2026-31633, CVE-2026-31636, CVE-2026-31705, CVE-2026-43198,\nCVE-2026-43379, CVE-2026-43465, CVE-2026-43499, CVE-2026-46113,\nCVE-2026-46137, CVE-2026-46242, CVE-2026-46290, CVE-2026-46317,\nCVE-2026-46331, CVE-2026-52924, CVE-2026-52989, CVE-2026-53086,\nCVE-2026-53131, CVE-2026-53176, CVE-2026-53212, CVE-2026-53225,\nCVE-2026-53228, CVE-2026-53277, CVE-2026-53359)\n","status":"published","published":"2026-08-21T19:59:28Z","modified":"2026-11-06T13:49:11.551849356Z","updated_at":"2026-11-06T14:26:46.957794Z"}]}}